linux-kernel - Re: [patch 2/3] isolcpus: affine kernel threads to specified cpumask

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:   Tue, 31 Mar 2020 15:36:38 +0200
From:   Frederic Weisbecker <frederic@...nel.org>
To:     Marcelo Tosatti <mtosatti@...hat.com>
Cc:     linux-kernel@...r.kernel.org,
        Frederic Weisbecker <fweisbec@...il.com>,
        Chris Friesen <chris.friesen@...driver.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Peter Zijlstra <peterz@...radead.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Jim Somerville <Jim.Somerville@...driver.com>,
        Christoph Lameter <cl@...ux.com>
Subject: Re: [patch 2/3] isolcpus: affine kernel threads to specified cpumask

On Tue, Mar 31, 2020 at 08:50:14AM -0300, Marcelo Tosatti wrote:
> On Tue, Mar 31, 2020 at 02:57:08AM +0200, Frederic Weisbecker wrote:
> > On Sat, Mar 28, 2020 at 12:21:19PM -0300, Marcelo Tosatti wrote:
> Hi Frederic,
> 
> > So, what about what I suggested with having "unbound" instead, which
> > includes all the CPU-unbound work?
> > 
> >  HK_FLAG_WQ | HK_FLAG_TIMER | HK_FLAG_RCU | HK_FLAG_MISC | HK_FLAG_KTHREAD | HK_FLAG_SCHED
> 
> After more thought, it would share certain flags with nohz_full=, which
> seemed confusing.

In fact I think we should also add HK_FLAG_KTHREAD | HK_FLAG_SCHED to nohz_full=

nohz_full is merely just a shortcut to isolate the tick and the unbound works anyway.

> 
> > (and yes your suggestion of including HK_FLAG_SCHED is good).
> > 
> > Because I don't see the point of exposing kthread isolation alone as an ABI
> > so far.
> > 
> > Later I suspect I'll turn all these flags into a single HK_FLAG_UNBOUND.
> 
> How about keeping the flags separate, and then on top of that do
> an "unbound" flag (less typing needed).
> 
> This would allow users to combine the individual flags (again, useful
> for debugging) while at the same time having an option which groups
> all the others?


Well, I'd rather not expose all the individual bits to the user. They rely
on kernel implementation details that shouldn't be much useful to the user.

As for internal kernel use, not sure this will ease debugging...

Thanks.