linux-kernel - Re: [PATCH] sched: track "isolated" cpus like other cpu masks.

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] [day] [month] [year] [list]

Message-ID: <4DDE821D.2010405@geoffthorpe.net>
Date:	Thu, 26 May 2011 12:38:53 -0400
From:	Geoff Thorpe <geoff@...ffthorpe.net>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched: track "isolated" cpus like other cpu masks.

On 11-05-23 04:14 PM, Peter Zijlstra wrote:
> On Fri, 2011-05-20 at 16:29 -0400, Geoff Thorpe wrote:
>> When a subset of cpus have been isolated, it can be useful for subsystems
>> or drivers that have cpu-affinity concerns to have access to this mask
>> (just like the other cpu masks; "possible", "present", "active" and
>> "online"). Eg. to provide specific handling for isolated cpus, or to
>> determine the non-isolated cpus (which is what sched.c uses it for).
>
> Nobody should be using that, isolated CPUs is a 'feature' slated for
> removal.
>

Ah OK, I wasn't aware of that. Consider the patch dropped then.

Thanks,
Geoff

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/