linux-kernel - Re: [RFC] cpuset: remove sched domain hooks from cpusets

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 11:23:06 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	"Martin Bligh" <mbligh@...gle.com>
Cc:	"Nick Piggin" <nickpiggin@...oo.com.au>,
	"Paul Jackson" <pj@....com>, akpm@...l.org, 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
Subject: Re: [RFC] cpuset: remove sched domain hooks from cpusets

On 10/19/06, Martin Bligh <mbligh@...gle.com> wrote:
>
> > I don't know of anyone else using cpusets, but I'd be interested to know.
>
> We (Google) are planning to use it to do some partitioning, albeit on
> much smaller machines. I'd really like to NOT use cpus_allowed from
> previous experience - if we can get it to to partition using separated
> sched domains, that would be much better.

Actually, what we'd really like is to be able to set cpus_allowed in
arbitrary ways (we're already doing this via sched_setaffinity() -
doing it via cpusets would just be an optimization when changing cpu
masks) and have the scheduler automatically do balancing efficiently.
In some cases sched domains might be appropriate, but in most of the
cases we have today, we have a job that's running with a CPU reserved
for itself but also has access to a "public" CPU, and some CPUs are
not public, but shared amongst a set of jobs. I'm not very familiar
with the sched domains code but I guess it doesn't handle overlapping
cpu masks very well?

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