linux-kernel - Re: [RFC] cpuset: add interface to isolated 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 21 Oct 2006 00:24:00 -0700
From:	Paul Jackson <pj@....com>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	akpm@...l.org, mbligh@...gle.com, menage@...gle.com,
	Simon.Derr@...l.net, linux-kernel@...r.kernel.org, dino@...ibm.com,
	rohitseth@...gle.com, holt@....com, dipankar@...ibm.com,
	suresh.b.siddha@...el.com, clameter@....com
Subject: Re: [RFC] cpuset: add interface to isolated cpus

> If you always have other domains overlapping them (regardless
> that it is a parent), then what actual use does cpu_exclusive
> flag have?

Good question.  To be a tad too honest, I don't consider it to be
all that essential.

It does turn out to be a bit useful, in that you can be confident that
if you are administering the batch scheduler and it has a cpu_exclusive
cpuset covering a big chunk of your system, then no other cpuset other
than the top cpuset right above, which you administer pretty tightly,
could have anything overlapping it.  You don't have to actually look
at the cpumasks in all the parallel cpusets and cross check each one
against the batch schedulers set of cpus for overlap.

But as you can see by grep'ing in kernel/cpuset.c, it is only used
to generate a couple of error returns, for things that you can do
just fine by turning off the cpu_exclusive flag.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.925.600.0401
-
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/