Parents (Total: 29)

The searched file hash is included in 29 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	7962A74EF90F9735FA133723E291EF5A
PackageArch	x86_64
PackageDescription	Out of memory killing has historically happened inside kernel space. On a memory overcommitted linux system, malloc(2) and friends usually never fail. However, if an application dereferences the returned pointer and the system has run out of physical memory, the linux kernel is forced take extreme measures, up to and including killing processes. This is sometimes a slow and painful process because the kernel can spend an unbounded amount of time swapping in and out pages and evicting the page cache. Furthermore, configuring policy is not very flexible while being somewhat complicated. oomd aims to solve this problem in userspace. oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainer	Fedora Project
PackageName	oomd
PackageRelease	2.fc33
PackageVersion	0.4.0
SHA-1	0583ACD232F49704DA5D6362335EF635D21E032C
SHA-256	F37929394B1C93D55018C5040FC3E494B69016845A4604E70B978BBB276DEFE5

Key	Value
FileSize	242772
MD5	124C378CF12FDB64D43E0EC0C84A23CB
PackageDescription	userspace Out-Of-Memory (OOM) killer for Linux systems oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainer	Yangfl <mmyangfl@gmail.com>
PackageName	oomd
PackageSection	admin
PackageVersion	0.5.0-1
SHA-1	08F2940F8912BBF8DB14127D04488876E95B60A3
SHA-256	A504CDDCEB558838CEAA9DC82B212106319C61900A1CD89BC33D00CD8B51E0E6

Key	Value
MD5	D47126105764F7FBE4353E5D99F17B34
PackageArch	aarch64
PackageDescription	Out of memory killing has historically happened inside kernel space. On a memory overcommitted linux system, malloc(2) and friends usually never fail. However, if an application dereferences the returned pointer and the system has run out of physical memory, the linux kernel is forced take extreme measures, up to and including killing processes. This is sometimes a slow and painful process because the kernel can spend an unbounded amount of time swapping in and out pages and evicting the page cache. Furthermore, configuring policy is not very flexible while being somewhat complicated. oomd aims to solve this problem in userspace. oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainer	Fedora Project
PackageName	oomd
PackageRelease	1.fc32
PackageVersion	0.3.2
SHA-1	098414B90DDD13B9B4AA3C8D84511925AC8DEBDB
SHA-256	A56F883598906BA9C77C6B46027C1102434CEDB4DB73F18F7B120E3BC9702DC4

Key	Value
FileSize	256104
MD5	1F0F8C6C979F5BC436134D9E20309437
PackageDescription	userspace Out-Of-Memory (OOM) killer for Linux systems oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainer	Yangfl <mmyangfl@gmail.com>
PackageName	oomd
PackageSection	admin
PackageVersion	0.5.0-1
SHA-1	20A7C630B17728FC26B649DF355C5865BBA98D25
SHA-256	D1713A5EF61F6CF58A53DD8F39E55B26B1B2AB440BE57693A4C74AFBA82F64D5

Key	Value
MD5	7382473E6DC775B052C297C62CCBB598
PackageArch	x86_64
PackageDescription	Out of memory killing has historically happened inside kernel space. On a memory overcommitted linux system, malloc(2) and friends usually never fail. However, if an application dereferences the returned pointer and the system has run out of physical memory, the linux kernel is forced take extreme measures, up to and including killing processes. This is sometimes a slow and painful process because the kernel can spend an unbounded amount of time swapping in and out pages and evicting the page cache. Furthermore, configuring policy is not very flexible while being somewhat complicated. oomd aims to solve this problem in userspace. oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainer	Fedora Project
PackageName	oomd
PackageRelease	1.fc32
PackageVersion	0.3.2
SHA-1	2DBB3A63827BB2584A2EF30A2A4BB25476BCCDDB
SHA-256	39AC9C1719E71D60840C9295246DE5766BAD5124F2DF1435D7BC8473BE3573B7

Key	Value
FileSize	165052
MD5	C5B87A9B6608B0737AAD97693F316581
PackageDescription	userspace Out-Of-Memory (OOM) killer for Linux systems oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainer	Yangfl <mmyangfl@gmail.com>
PackageName	oomd
PackageSection	admin
PackageVersion	0.4.0-1+b1
SHA-1	3187F5C0726B3C0E2218AF6114EB01FEC7EFD02E
SHA-256	0BFFE9A4C5710B859DB2162636A5069CA5FEBA2600B0FEAD57C97A2D37F0426C

Key	Value
MD5	09D0C557C7B28132790CF8386DFAA387
PackageArch	aarch64
PackageDescription	Out of memory killing has historically happened inside kernel space. On a memory overcommitted linux system, malloc(2) and friends usually never fail. However, if an application dereferences the returned pointer and the system has run out of physical memory, the linux kernel is forced take extreme measures, up to and including killing processes. This is sometimes a slow and painful process because the kernel can spend an unbounded amount of time swapping in and out pages and evicting the page cache. Furthermore, configuring policy is not very flexible while being somewhat complicated. oomd aims to solve this problem in userspace. oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainer	Fedora Project
PackageName	oomd
PackageRelease	2.fc33
PackageVersion	0.4.0
SHA-1	364ABD84FFDA5EC084FC49639BB81D947AFED472
SHA-256	C8D6465F3D786F2B43446FABACE85B64F420B251F6FF4CE44FD5046C0D015CF8

Key	Value
FileSize	254676
MD5	F947E5AF2F18579D2F8AFFBD49A7CC8D
PackageDescription	userspace Out-Of-Memory (OOM) killer for Linux systems oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainer	Yangfl <mmyangfl@gmail.com>
PackageName	oomd
PackageSection	admin
PackageVersion	0.5.0-1
SHA-1	3AE637D3CC44773E87816D66EA76C9F5FA34A75F
SHA-256	AC5A2651AF32C2598E73276937A825C301261DB5F5BF6FD9349197B6A54AD1AE

Key	Value
FileSize	281168
MD5	47F9C8FD025024FBC09C791FB26DAE3F
PackageDescription	userspace Out-Of-Memory (OOM) killer for Linux systems oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainer	Yangfl <mmyangfl@gmail.com>
PackageName	oomd
PackageSection	admin
PackageVersion	0.5.0-1
SHA-1	3FE678F0EC7046441E928E377527C337C133EEE3
SHA-256	E26C49FC32386F0518E56307E86D910C061E231BD14C6D9753383D3A533C16DE

Key	Value
MD5	73D4E3CEA225CA16C76BA70EB55E7BC1
PackageArch	x86_64
PackageDescription	Out of memory killing has historically happened inside kernel space. On a memory overcommitted linux system, malloc(2) and friends usually never fail. However, if an application dereferences the returned pointer and the system has run out of physical memory, the linux kernel is forced take extreme measures, up to and including killing processes. This is sometimes a slow and painful process because the kernel can spend an unbounded amount of time swapping in and out pages and evicting the page cache. Furthermore, configuring policy is not very flexible while being somewhat complicated. oomd aims to solve this problem in userspace. oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainer	Fedora Project
PackageName	oomd
PackageRelease	1.el8
PackageVersion	0.5.0
SHA-1	50B56BD309285D2269848832964DFE5BF248E3ED
SHA-256	254341D88ECC137702ED124E2A7B0F241EE7C1F60FF6758848E037FBCD935DA9