Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/systemd: hybrid cgroupfs hierarchy for docker compatibility
Date: Mon, 11 Nov 2019 16:01:58 +0100	[thread overview]
Message-ID: <20191111160158.20956982@windsurf.home> (raw)
In-Reply-To: <CAFvCimWdoHfPzVJchnczcBnk1VECW+N_1c21fvOuQRosGkQbrQ@mail.gmail.com>

Hello,

(If possible, you should bottom post instead of top post. Thanks!)

On Mon, 11 Nov 2019 15:56:04 +0100
J?r?my ROSEN <jeremy.rosen@smile.fr> wrote:

> It's about what implementation of cgroup is used by systemd to maintain the
> cgroup-tree of processes
> 
> * legacy is v1
> * hybrid is both v1 and v2
> * unified is v2 only
> (note that only the default is changed, this can be changed via the kernel
> command-line at boot time)
> 
> v1 is deprecated on the kernel side because it was... a mess.
> The systemd people are migrating stuff from v1 to v2 as new controllers are
> added to v2, but at this point there is little left that is v1 only thus
> the change of the default value
> 
> Very few user-space projects care about cgroups : mainly systemd and
> container-managers. Container-manager need to interact with systemd as
> described in
> https://systemd.io/CGROUP_DELEGATION.html which allows to drop v1 and to
> correctly spread the responsibility between systemd and the container
> managers without
> stepping on each other's toes.
> Also note that Fedora31 will use the unified cgroup hierarchy.
> A good summary of adoption status :
> https://medium.com/nttlabs/cgroup-v2-596d035be4d7
> 
> At that point, I think staying in hybrid mode is the safest bet :
> everything in user-space hasn't migrated yet.
> Let Fedora take the fire and force everybody to migrate, and let's revisit
> the subject once (at least) Docker has migrated...

OK, thanks a lot for this explanation, much clearer!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-11-11 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11  8:33 [Buildroot] [PATCH 1/1] package/systemd: hybrid cgroupfs hierarchy for docker compatibility Christian Stewart
2019-11-11  9:04 ` James Hilliard
2019-11-11 10:09   ` Jérémy ROSEN
2019-11-11 14:39     ` Thomas Petazzoni
2019-11-11 14:56       ` Jérémy ROSEN
2019-11-11 15:01         ` Thomas Petazzoni [this message]
2019-11-11 15:29 ` Thomas Petazzoni
2019-11-11 20:27   ` Christian Stewart

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=20191111160158.20956982@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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