On Mon, 13 Jul 2026 at 20:52, Ishaan Desai via lists.openembedded.org <[email protected]> wrote: > Adds a CLI tool and bbclass for applying per-service memory limits via > systemd resource control and Linux cgroups v2. > > The memory-control command inspects MemoryMax and MemoryHigh settings > for any running systemd service and lists all services with a drop-in > applied. > > memory-control.bbclass allows any recipe to set a memory limit at build > time by inheriting the class and setting MEMORY_LIMIT. Two OOM policies > are available via MEMORY_OOM_POLICY: "reboot" (default) reboots on OOM, > and "kill" terminates only the offending process. > > The recipe requires the systemd DISTRO_FEATURE via features_check so it > is cleanly skipped on non-systemd distros. The bbclass guards its > RDEPENDS injection with bb.utils.contains for the same reason.
Note that the question from RP is still standing, and without an answer, this is not going to be accepted. There's a lot of possible resource control mechanisms, this doesn't mean oe-core should carry them. Should this perhaps be proposed directly to systemd upstream first? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#240893): https://lists.openembedded.org/g/openembedded-core/message/240893 Mute This Topic: https://lists.openembedded.org/mt/120210280/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
