Parents (Total: 3)

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

Key	Value
FileSize	188144
MD5	072267C931AECDF4C3D69BB16746055F
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	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	oomd
PackageSection	admin
PackageVersion	0.3.1-1
SHA-1	A6A8AF691E2D6588C0AE80FE21F437F19C4FE5A9
SHA-256	139834516EF368AD3ED15D880648ADEC1F48D00216A4E164B7DD132C756B1A9D

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
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