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:	Fri, 20 Oct 2006 16:14:04 -0700
From:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
To:	Dinakar Guniguntala <dino@...ibm.com>, pj@....com
Cc:	Paul Jackson <pj@....com>, nickpiggin@...oo.com.au,
	mbligh@...gle.com, akpm@...l.org, menage@...gle.com,
	Simon.Derr@...l.net, linux-kernel@...r.kernel.org,
	rohitseth@...gle.com, holt@....com, dipankar@...ibm.com,
	suresh.b.siddha@...el.com, clameter@....com
Subject: Re: [RFC] cpuset: remove sched domain hooks from cpusets

How about something like use_cpus_exclusive flag in cpuset?

And whenever a child cpuset sets this use_cpus_exclusive flag, remove
those set of child cpuset cpus from parent cpuset and also from the
tasks which were running in the parent cpuset. We can probably  allow this
to happen as long as parent cpuset has atleast one cpu.

And if this use_cpus_exclusive flag is cleared in cpuset, its pool of cpus will
be returned to the parent. We can perhaps have cpus_owned inaddition to
cpus_allowed to reflect what is being exclusively used
and owned(which combines all the exclusive cpus used by the parent and children)

So effectively, a sched domain parition will get defined for each
cpuset having 'use_cpus_exclusive'.

And this is mostly inline with what anyone can expect from exclusive
cpu usage in a cpuset right?

Job manager/administrator/owner of the cpusets can set/reset the flags
depending on what cpusets/jobs are active.

Paul will this address your needs?

thanks,
suresh
-
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/