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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7a45fadb-edc2-f8f2-f0e3-54bd9b24e156@maciej.szmigiero.name>
Date:   Mon, 8 Jan 2018 17:29:42 +0100
From:   "Maciej S. Szmigiero" <mail@...iej.szmigiero.name>
To:     Tejun Heo <tj@...nel.org>
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 08.01.2018 13:15, Tejun Heo wrote:
> 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?

Will do.

> Thanks.
> 

Maciej

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ