linux-kernel - Re: [RFC PATCH 01/12] housekeeping: Move housekeeping related code to its own file

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: <20170831225816.GA18249@lerouge>
Date:   Fri, 1 Sep 2017 00:58:18 +0200
From:   Frederic Weisbecker <fweisbec@...il.com>
To:     Rik van Riel <riel@...hat.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Chris Metcalf <cmetcalf@...lanox.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Luiz Capitulino <lcapitulino@...hat.com>,
        Christoph Lameter <cl@...ux.com>,
        "Paul E . McKenney" <paulmck@...ux.vnet.ibm.com>,
        Ingo Molnar <mingo@...nel.org>, Mike Galbraith <efault@....de>,
        Wanpeng Li <kernellwp@...il.com>
Subject: Re: [RFC PATCH 01/12] housekeeping: Move housekeeping related code
 to its own file

On Thu, Aug 31, 2017 at 04:16:16PM -0400, Rik van Riel wrote:
> On Wed, 2017-08-23 at 03:51 +0200, Frederic Weisbecker wrote:
> > The housekeeping code is currently tied to the nohz code. As we are
> > planning to make housekeeping independant from it, start with moving
> > the relevant code to its own file.
> > 
> Why are nohz full and housekeeping being
> decoupled from each other?
> 
> Won't people want to use them together?
> 
> What use case am I missing?

So nohz is really just a feature and it shouldn't decide about other isolation
features. It should be the opposite: isolation picks up nohz, alongside other
isolation things. I think we did a layering misdesign. So it's mostly just a code
reorganisation.

While at it, isolcpus= is also part of the isolation toolset. So I thought we should
centralize all this isolation code in a common subsystem.