On Fri, 2026-07-10 at 12:05 -0500, Ishaan Desai via lists.openembedded.org 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. > > AI-Generated: Uses IBM Bob > > Signed-off-by: Ishaan Desai <[email protected]> > --- > meta/classes-recipe/memory-control.bbclass | 95 +++++++++ > .../memory-control/cgroups-v2.cfg | 19 ++ > .../memory-control/memory-control.sh | 196 ++++++++++++++++++ > .../memory-control/[email protected] | 13 ++ > .../memory-control/memory-control_1.0.bb | 53 +++++ > 5 files changed, 376 insertions(+) > create mode 100644 meta/classes-recipe/memory-control.bbclass > create mode 100644 > meta/recipes-support/memory-control/memory-control/cgroups-v2.cfg > create mode 100755 > meta/recipes-support/memory-control/memory-control/memory-control.sh > create mode 100644 > meta/recipes-support/memory-control/memory-control/[email protected] > create mode 100644 meta/recipes-support/memory-control/memory-control_1.0.bb
Why a top level bbclass and not just part of the recipe or an .inc file? What is the justification for this code in OE-Core? Who is going to use it and who is going to maintain it? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#240723): https://lists.openembedded.org/g/openembedded-core/message/240723 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]] -=-=-=-=-=-=-=-=-=-=-=-
