From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Wolfgang Bumiller <w.bumiller@proxmox.com>
Subject: [pve-devel] applied: [PATCH container] configure cpu/cpuset/memory cgroupv2 values
Date: Tue, 15 Jun 2021 14:39:31 +0200 [thread overview]
Message-ID: <e07db805-f18a-f781-e1b6-c351cb16dbb2@proxmox.com> (raw)
In-Reply-To: <20210610111516.90018-1-w.bumiller@proxmox.com>
On 10.06.21 13:15, Wolfgang Bumiller wrote:
> While the hotplug code utilized PVE::CGroup and already
> supported cgroupv2 with this, we did not write out the
> configuration before.
>
> Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
> ---
> These values should correspond to how the PVE::CGroup live-apply code
> works.
>
> After this there's 1 more missing piece for pure-cgroup2 systems:
> handling the devices we currently handle in the autodev hook. This is
> very different in cgv2.
>
> src/PVE/LXC.pm | 34 +++++++++++++++++++++++++++-------
> src/lxc-pve-prestart-hook | 3 ++-
> 2 files changed, 29 insertions(+), 8 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2021-06-15 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 11:15 [pve-devel] " Wolfgang Bumiller
2021-06-15 12:39 ` Thomas Lamprecht [this message]
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=e07db805-f18a-f781-e1b6-c351cb16dbb2@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=w.bumiller@proxmox.com \
/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