linux-kernel - Re: [PATCH][RESEND] cgroup, docs: document the root cgroup behavior of cpu and io controllers

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180108121503.GK3668920@devbig577.frc2.facebook.com>
Date:   Mon, 8 Jan 2018 04:15:03 -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][RESEND] cgroup, docs: document the root cgroup behavior
 of cpu and io controllers

Hello,

On Thu, Jan 04, 2018 at 10:57:00PM +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.

I don't think we want to fully guarantee the current behavior.  On the
scheduler side, I don't think it's likely to change but blkio side
*might* change.  Can you please collect the root behavior in a separte
section and clearly note that the behaviors are subject to change?

Thanks.

-- 
tejun