From: Paul Jackson <pj@sgi.com>
To: Paul Jackson <pj@sgi.com>
Cc: dino@in.ibm.com, nickpiggin@yahoo.com.au, akpm@osdl.org,
mbligh@google.com, menage@google.com, Simon.Derr@bull.net,
linux-kernel@vger.kernel.org, rohitseth@google.com, holt@sgi.com,
dipankar@in.ibm.com, suresh.b.siddha@intel.com
Subject: Re: [RFC] cpuset: Explicit dynamic sched domain cpuset flag
Date: Tue, 31 Oct 2006 15:58:19 -0800 [thread overview]
Message-ID: <20061031155819.29621173.pj@sgi.com> (raw)
In-Reply-To: <20061031064300.10a97c13.pj@sgi.com>
pj wrote:
> 9) Finally, we really do need a way, on a production system, for user
> space to ask the kernel where load balancing is limited.
>
> For example one possible interface would have user space pass a
> cpumask to the kernel, and get back a Boolean value, indicating
> whether or not there are any limitations on load balancing between
> any two CPUs specified in that cpumask.
Ah - a simpler API, more user friendly, more "cpuset API style"
friendly:
A read-only, per-cpuset Boolean flag that indicates whether the
scheduler is fully load balancing across all 'cpus' of that cpuset.
Internally, the kernel would answer this by seeing whether or
not the cpusets cpus_allowed cpumask was a subset of one of the
members of the scheduler domains partition.
Call this per-cpuset flag something such as:
sched_is_fully_load_balanced # read-only Boolean
This goes along with having the control flag named something such as:
sched_ok_not_to_load_balance # read-write Boolean
If a task was in a cpuset that had 'sched_is_fully_load_balanced'
False, then it might not get load balanced.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-10-31 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 21:26 [RFC] cpuset: Remove sched domain hooks from cpusets Dinakar Guniguntala
2006-10-30 21:29 ` [RFC] cpuset: Explicit dynamic sched domain cpuset flag Dinakar Guniguntala
2006-10-31 14:43 ` Paul Jackson
2006-10-31 23:58 ` Paul Jackson [this message]
2006-11-08 10:38 ` Paul Jackson
2006-11-08 18:23 ` Dinakar Guniguntala
2006-11-08 21:22 ` Paul Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061031155819.29621173.pj@sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=dino@in.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--cc=rohitseth@google.com \
--cc=suresh.b.siddha@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox