From: Tejun Heo <tj@kernel.org>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Corbet <corbet@lwn.net>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] cgroup, docs: document the root cgroup behavior of cpu and io controllers
Date: Tue, 16 Jan 2018 08:08:02 -0800 [thread overview]
Message-ID: <20180116160802.GO3460072@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <90ac05c0-8e84-0c0b-195a-4c1712e40f09@maciej.szmigiero.name>
On Wed, Jan 10, 2018 at 11:33:19PM +0100, Maciej S. Szmigiero wrote:
> Currently, cgroups v2 documentation contains only a generic remark that
> "How resource consumption in the root cgroup is governed is up to each
> controller", which isn't really telling users much, who need to dig in the
> code and / or commit messages to learn the exact behavior.
>
> In cgroups v1 at least the blkio controller had its operation with respect
> to competition between child threads and child cgroups documented in
> blkio-controller.txt, with references to cfq-iosched.txt.
> Also, cgroups v2 documentation describes v1 behavior of both cpu and
> blkio controllers in an "Issues with v1" section.
>
> Let's document this behavior also for cgroups v2 to make life easier for
> users.
>
> Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
Applied to cgroup/for-4.16.
Thanks.
--
tejun
prev parent reply other threads:[~2018-01-16 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 22:33 [PATCH v2] cgroup, docs: document the root cgroup behavior of cpu and io controllers Maciej S. Szmigiero
2018-01-16 16:08 ` Tejun Heo [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=20180116160802.GO3460072@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mail@maciej.szmigiero.name \
/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