From: Johannes Weiner <hannes@cmpxchg.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Tejun Heo <tj@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
Li Zefan <lizefan@huawei.com>, Jonathan Corbet <corbet@lwn.net>,
cgroups@vger.kernel.org,
Android Kernel Team <kernel-team@android.com>,
Rom Lemarchand <romlem@android.com>,
Colin Cross <ccross@android.com>
Subject: Re: [RFC][PATCH 0/2] Android style loosening of cgroup attach permissions
Date: Thu, 4 Jun 2015 14:36:58 -0400 [thread overview]
Message-ID: <20150604183658.GA5682@cmpxchg.org> (raw)
In-Reply-To: <CALAqxLWkXTgKzq68H6TvPc6Wgbn5_jwVoW5Q9onnHnvQ0bTNiA@mail.gmail.com>
On Thu, Jun 04, 2015 at 10:11:17AM -0700, John Stultz wrote:
> On Tue, Jun 2, 2015 at 10:50 PM, Tejun Heo <tj@kernel.org> wrote:
> > memcg usage came up a while ago and there wasn't anything major which
> > can't be achieved (usually better) by following more standard cgroup
> > usage - changing knobs rather than moving tasks around.
>
> Do you have a pointer to that discussion or maybe even just a sense of
> who was involved so I can trawl the list and better understand it?
I wrote a lengthy explanation of why moving tasks between cgroups is
problematic from a memcg view: https://lkml.org/lkml/2014/12/19/358
Rather than creating super-cgroups as configuration domains and using
migration as a reconfiguration mechanism, it's much better to group
tasks per app and reconfigure the groups themselves using specific
presets for classes of apps, like foreground, background, audio.
next prev parent reply other threads:[~2015-06-04 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 3:41 John Stultz
2015-05-21 3:41 ` [RFC][PATCH 1/2] cgroup: Add generic cgroup subsystem permission checks John Stultz
2015-05-21 3:41 ` [RFC][PATCH 2/2] cgroup: Add a memcg and cpu cg allow_attach policy for Android John Stultz
2015-06-02 19:07 ` [RFC][PATCH 0/2] Android style loosening of cgroup attach permissions John Stultz
2015-06-03 5:50 ` Tejun Heo
2015-06-04 17:11 ` John Stultz
2015-06-04 18:36 ` Johannes Weiner [this message]
2015-06-05 21:28 ` John Stultz
2015-06-05 21:33 ` John Stultz
2015-06-04 18:52 ` Tejun Heo
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=20150604183658.GA5682@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=ccross@android.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=romlem@android.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®