From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ishaan.Desai@ibm.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] memory-control: add recipe and bbclass for cgroup v2 memory limiting
Date: Sat, 11 Jul 2026 21:27:54 +0100 [thread overview]
Message-ID: <54968e21199487c82f2e6067da717f25ed3de7bf.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260710170500.3863193-1-Ishaan.Desai@ibm.com>
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 <Ishaan.Desai@ibm.com>
> ---
> meta/classes-recipe/memory-control.bbclass | 95 +++++++++
> .../memory-control/cgroups-v2.cfg | 19 ++
> .../memory-control/memory-control.sh | 196 ++++++++++++++++++
> .../memory-control/memory-control@.service | 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/memory-control@.service
> 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
next prev parent reply other threads:[~2026-07-11 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 17:05 [PATCH] memory-control: add recipe and bbclass for cgroup v2 memory limiting Ishaan Desai
2026-07-11 18:21 ` [OE-core] " Mathieu Dubois-Briand
2026-07-11 20:27 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-13 18:51 Ishaan Desai
2026-07-14 12:49 ` [OE-core] " Mathieu Dubois-Briand
2026-07-14 13:32 ` Alexander Kanavin
2026-07-14 16:35 ` Ishaan Desai
2026-07-14 16:53 ` [OE-core] " Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54968e21199487c82f2e6067da717f25ed3de7bf.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Ishaan.Desai@ibm.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox