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  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 <>
To:     Waiman Long <>
Cc:     Li Zefan <>,
        Johannes Weiner <>,
        Jonathan Corbet <>,,,,
        Mike Galbraith <>,
        Christian Brauner <>,
        St├ęphane Graber <>,
        Serge Hallyn <>
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

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.


Powered by blists - more mailing lists