All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 14 Jul 2026 14:49:54 +0200	[thread overview]
Message-ID: <DJYB230VVFGI.3OG933GRJ4M1D@bootlin.com> (raw)
In-Reply-To: <20260713185154.4171585-1-Ishaan.Desai@ibm.com>

On Mon Jul 13, 2026 at 8:51 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.
>
> 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.
>
> AI-Generated: Uses IBM Bob
>
> Signed-off-by: Ishaan Desai <Ishaan.Desai@ibm.com>

Hi Ishaan,

Thanks for your patch.

We get a warning about this new recipe during the build:

WARNING: lib32-memory-control-1.0-r0 do_unpack: lib32-memory-control: the directory ${UNPACKDIR}/${BP} (/srv/pokybuild/yocto-worker/qemux86-world-alt/build/build/tmp/work/x86-pokymllib32-linux/lib32-memory-control/1.0/sources/memory-control-1.0) pointed to by the S variable doesn't exist - please set S within the recipe to point to where the source has been unpacked to

https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/3970
https://autobuilder.yoctoproject.org/valkyrie/#/builders/25/builds/4125

Can you make sure everything is correct?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-07-14 12:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 18:51 [PATCH] memory-control: add recipe and bbclass for cgroup v2 memory limiting Ishaan Desai
2026-07-14 12:49 ` Mathieu Dubois-Briand [this message]
2026-07-14 13:32 ` [OE-core] " Alexander Kanavin
2026-07-14 16:35   ` Ishaan Desai
2026-07-14 16:53     ` [OE-core] " Alexander Kanavin
2026-07-14 18:33       ` Ishaan Desai
2026-07-14 16:43 ` [PATCH v3] " Ishaan Desai
2026-07-14 16:45   ` Ishaan Desai
  -- strict thread matches above, loose matches on Subject: below --
2026-07-10 17:05 [PATCH] " Ishaan Desai
2026-07-11 18:21 ` [OE-core] " Mathieu Dubois-Briand
2026-07-11 20:27 ` Richard Purdie

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=DJYB230VVFGI.3OG933GRJ4M1D@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.