linux-kernel - Re: [PATCH] cpuset: Allow v2 behavior in v1 cgroup

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]

Date:   Wed, 16 Aug 2017 09:20:27 +0800
From:   Zefan Li <lizefan@...wei.com>
To:     Waiman Long <longman@...hat.com>, Tejun Heo <tj@...nel.org>,
        "Johannes Weiner" <hannes@...xchg.org>,
        Jonathan Corbet <corbet@....net>
CC:     <linux-kernel@...r.kernel.org>, <linux-doc@...r.kernel.org>
Subject: Re: [PATCH] cpuset: Allow v2 behavior in v1 cgroup

On 2017/8/16 1:27, Waiman Long wrote:
> Cpuset v2 has some valuable attributes that are not present in
> v1 because of backward compatibility concern. One of that is the
> restoration of the original cpu and memory node mask after a hot
> removal and addition event sequence.
> 
> This patch adds a new kernel command line option "cpuset_v2_mode=" to
> allow cpuset to have v2 behavior in a v1 cgroup when using a non-zero
> value. This enables users to optionally enable cpuset v2 behavior if
> they choose to.
> 
> Signed-off-by: Waiman Long <longman@...hat.com>

I have no strong objection. I have received quite a few requests for
this in the past, and some were from other departments in my company.