From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
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 20:21:23 +0200 [thread overview]
Message-ID: <DJVY88YLD7A6.280XMNFRJSUGE@bootlin.com> (raw)
In-Reply-To: <20260710170500.3863193-1-Ishaan.Desai@ibm.com>
On Fri Jul 10, 2026 at 7:05 PM CEST, 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>
> ---
Hi Ishaan,
Thanks for your patch.
It looks like this is breaking builds on some platforms:
ERROR: Nothing RPROVIDES 'systemd' (but /srv/pokybuild/yocto-worker/no-x11/build/layers/openembedded-core/meta/recipes-support/memory-control/memory-control_1.0.bb RDEPENDS on or otherwise requires it)
systemd was skipped: using DISTRO 'poky', which is missing required DISTRO_FEATURES: 'usrmerge systemd'
NOTE: Runtime target 'systemd' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['systemd']
NOTE: Runtime target 'memory-control' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['memory-control', 'systemd']
ERROR: Nothing RPROVIDES 'memory-control-dev' (but /srv/pokybuild/yocto-worker/no-x11/build/layers/openembedded-core/meta/recipes-support/memory-control/memory-control_1.0.bb RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'memory-control-dev'
NOTE: Runtime target 'memory-control-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['memory-control-dev']
https://autobuilder.yoctoproject.org/valkyrie/#/builders/25/builds/4115
https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/4141
https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/7643378/raw_inline
Also, please add the corresponding entry in
meta/conf/distro/include/maintainers.inc.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-07-11 18:21 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 ` Mathieu Dubois-Briand [this message]
2026-07-11 20:27 ` [OE-core] " Richard Purdie
-- 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=DJVY88YLD7A6.280XMNFRJSUGE@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--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