lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180116160802.GO3460072@devbig577.frc2.facebook.com>
Date:   Tue, 16 Jan 2018 08:08:02 -0800
From:   Tejun Heo <tj@...nel.org>
To:     "Maciej S. Szmigiero" <mail@...iej.szmigiero.name>
Cc:     Li Zefan <lizefan@...wei.com>,
        Johannes Weiner <hannes@...xchg.org>,
        Jonathan Corbet <corbet@....net>, cgroups@...r.kernel.org,
        linux-doc@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] cgroup, docs: document the root cgroup behavior of
 cpu and io controllers

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@...iej.szmigiero.name>

Applied to cgroup/for-4.16.

Thanks.

-- 
tejun

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ