From: "Ishaan Desai" <Ishaan.Desai@ibm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] memory-control: add recipe and bbclass for cgroup v2 memory limiting
Date: Tue, 14 Jul 2026 11:33:33 -0700 [thread overview]
Message-ID: <783427.1784054013995242828@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj-iVhChLSJxraiwHo3f5Unvu-N6MyQo1KcHSuNKRG2EzA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
Hi Alexander,
Thanks for the feedback. I'll move this out of OE-Core. Is there an existing small layer this would fit into, or would you expect this to warrant a new dedicated layer? I'll also add tests and usage examples before resubmitting. I'll drop the bbclass and implement a memory-control-config recipe that installs the needed systemd configuration without touching the recipes that provide the actual services.
I hadn't fully considered the licensing implications there. I'll rewrite the control logic to avoid a bash dependency by extending the existing systemd tooling directly rather than shipping a separate CLI. I'll put together a revised version along these lines and send it out for another look. Thanks again for the advice.
Thanks,
Ishaan Desai
**
[-- Attachment #2: Type: text/html, Size: 4941 bytes --]
next prev parent reply other threads:[~2026-07-14 18:33 UTC|newest]
Thread overview: 9+ 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 ` [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
2026-07-14 18:33 ` Ishaan Desai [this message]
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
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=783427.1784054013995242828@lists.openembedded.org \
--to=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.