linux-kernel - Re: [RFC] Cpuset: explicit dynamic sched domain control flags

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: <453732CF.7050801@yahoo.com.au>
Date:	Thu, 19 Oct 2006 18:09:51 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Paul Jackson <pj@....com>
CC:	suresh.b.siddha@...el.com, dino@...ibm.com, menage@...gle.com,
	Simon.Derr@...l.net, linux-kernel@...r.kernel.org,
	mbligh@...gle.com, rohitseth@...gle.com, dipankar@...ibm.com
Subject: Re: [RFC] Cpuset: explicit dynamic sched domain control flags

Paul Jackson wrote:
> Nick wrote:
> 
>>You don't have to worry about the details of the hierarchy. You just need
>>to know where the partitions are
> 
> 
> Cpusets is a hierarchical space.  What happens in a subtree
> of the /dev/cpuset hierarchy should not be affecting others.
> 
> Partitioning sched domains is a flat space - dividing the
> CPUs of a system into disjoint partitions.
> 
> Using details deep in the cpuset hierarchy to define global
> partitions leads to chaos in the minds of those coming at
> this from the cpuset side.

So don't do it, then. Just do the partitioning for disjoint
cpusets off the root cpuset, if you like. Or don't use it at
all, even.

But please don't let *users* try to deal with it.

> The lack of any means on a production system to view the
> resulting partition leads to ignorance of how deep is the
> chaos, a dangerous state of affairs.

It is much less complex than cpusets, as you note it is a flat
space.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 
-
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/