linux-kernel - Re: [PATCH v3] cpuset: Enable cpuset controller in default hierarchy

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:   Thu, 26 Oct 2017 07:39:08 -0700
From:   Tejun Heo <tj@...nel.org>
To:     Waiman Long <longman@...hat.com>
Cc:     Li Zefan <lizefan@...wei.com>,
        Johannes Weiner <hannes@...xchg.org>,
        Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
        cgroups@...r.kernel.org, linux-doc@...r.kernel.org,
        Mike Galbraith <efault@....de>,
        Christian Brauner <christian.brauner@...onical.com>,
        Stéphane Graber <stgraber@...ntu.com>,
        Serge Hallyn <serge@...lyn.com>
Subject: Re: [PATCH v3] cpuset: Enable cpuset controller in default hierarchy

Hello, Waiman.

On Wed, Oct 25, 2017 at 11:50:34AM -0400, Waiman Long wrote:
> Ping! Any comment on this patch?

Sorry about the lack of response.  Here are my two thoughts.

1. I'm not really sure about the memory part.  Mostly because of the
   way it's configured and enforced is completely out of step with how
   mm behaves in general.  I'd like to get more input from mm folks on
   this.

2. I want to think more about how we expose the effective settings.
   Not that anything is wrong with what cpuset does, but more that I
   wanna ensure that it's something we can follow in other cases where
   we have similar hierarchical property propagation.

We're likely too late for the coming merge window.  Let's handle it
during the next window.

Thanks and my apologies for the delay.

-- 
tejun