linux-kernel - Re: [RFC] Restrict kernel spawning of threads to a specified set of cpus.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Sep 2013 14:21:06 +0000
From:	Christoph Lameter <cl@...ux.com>
To:	Mike Galbraith <bitbucket@...ine.de>
cc:	Gilad Ben-Yossef <gilad@...yossef.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Mike Frysinger <vapier@...too.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [RFC] Restrict kernel spawning of threads to a specified set of
 cpus.

On Wed, 11 Sep 2013, Mike Galbraith wrote:

> Mind saying why?  To me, creating properties of exclusive sets of CPUs
> that the interface which manages sets and their properties is not fully
> aware of is a dainbramaged thing to do.

cpusets is being replaced by cgropus. And the mechanism adds some
significant latencies to core memory management processing path.

Also many folks in finance like to deal directly with the hardware
(processor numbers, affinity masks etc). There are already numerous ways
to specify these masks. Pretty well established. Digging down a cpuset
hierachy is a bit tedious. Then these cpusets can also overlap which
makes the whole setup difficult.

If cpusets can be used on top then ok but I would like it not to be
required to have that compiled in.

--
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/