Parents (Total: 4)

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

Key	Value
MD5	5508CC3B6339C000FF0CB36D48E5F7F8
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	6.fc34
PackageVersion	0.4.0
SHA-1	F9B4FB11CF4C036BBDD47E3346905C9282E42C8C
SHA-256	1B839C62C73729A7AEA92F64745A22CC7A031E173D0C0CD6C49D16B4D4C89515

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
MD5	D1E10507AF5DCCC2A96815191FB54C88
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	6.fc34
PackageVersion	0.4.0
SHA-1	7249CE0F094D4BC5A94BBDE088B38254D9CA32AE
SHA-256	65F38939DC8CA16BC56CFA31DCAB432284EAA39F0F11519BA26A7205594BE357

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