From: Johannes Weiner <hannes@cmpxchg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@kernel.org>,
mm-commits@vger.kernel.org, tj@kernel.org, guro@fb.com,
dennis@kernel.org, chris@chrisdown.name,
cgroups mailinglist <cgroups@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: + mm-consider-subtrees-in-memoryevents.patch added to -mm tree
Date: Wed, 22 May 2019 11:44:23 -0400 [thread overview]
Message-ID: <20190522154423.GA24972@cmpxchg.org> (raw)
In-Reply-To: <20190521192351.4d3fd16c6f0e6a0b088779a6@linux-foundation.org>
On Tue, May 21, 2019 at 07:23:51PM -0700, Andrew Morton wrote:
> On Fri, 17 May 2019 21:33:48 -0400 Johannes Weiner <hannes@cmpxchg.org> wrote:
>
> > - Adoption data suggests that cgroup2 isn't really used yet. RHEL8 was
> > just released with cgroup1 per default. Fedora is currently debating
> > a switch. None of the other distros default to cgroup2. There is an
> > article on the lwn frontpage *right now* about Docker planning on
> > switching to cgroup2 in the near future. Kubernetes is on
> > cgroup1. Android is on cgroup1. Shakeel agrees that Facebook is
> > probably the only serious user of cgroup2 right now. The cloud and
> > all mainstream container software is still on cgroup1.
>
> I'm thinking we need a cc:stable so these forthcoming distros are more
> likely to pick up the new behaviour?
Yup, makes sense to me. Thank you!
next prev parent reply other threads:[~2019-05-22 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190212224542.ZW63a%akpm@linux-foundation.org>
2019-02-13 12:47 ` + mm-consider-subtrees-in-memoryevents.patch added to -mm tree Michal Hocko
2019-05-16 17:56 ` Johannes Weiner
2019-05-16 18:10 ` Michal Hocko
2019-05-16 19:39 ` Johannes Weiner
2019-05-17 12:33 ` Michal Hocko
2019-05-17 13:00 ` Shakeel Butt
2019-05-22 5:30 ` Suren Baghdasaryan
2019-05-18 1:33 ` Johannes Weiner
2019-05-22 2:23 ` Andrew Morton
2019-05-22 15:44 ` Johannes Weiner [this message]
2019-05-17 13:00 ` Shakeel Butt
2019-05-17 19:04 ` Johannes Weiner
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=20190522154423.GA24972@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=dennis@kernel.org \
--cc=guro@fb.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=tj@kernel.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.