public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Lse-tech] Re: CPUSET Proposal
Date: Thu, 25 Sep 2003 18:49:52 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106451631727404@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106444308519469@msgid-missing>

> You could also do a big chunk of this by allowing normal 
> privledge users
> to sched_setaffinity() a *subset* of their current allowed 
> CPU set, but
> not expand it.  sched_setaffinity() isn't *that* old of an 
> interface, so
> I'm not sure why you can't just change the application at 
> this point.  

Because you need virtual cpu numbers.  Suppose I have a 16-way
system, and *two* applications that know nothing about each other,
but each happens to want 5 cpus to run.

With cpusets each application can ask the kernel for 5 cpus
(or a wrapper that invokes the application can do so), and then
the application can happily divide its work between virtual cpus
0, 1, 2, 3, 4 (using sched_setaffinity()).  The kernel can be smart
and provide different physical cpus for each of the cpusets.

-Tony

  parent reply	other threads:[~2003-09-25 18:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 22:26 [Lse-tech] Re: CPUSET Proposal Hanna Linder
2003-09-25  5:39 ` Paul Jackson
2003-09-25  5:48 ` William Lee Irwin III
2003-09-25  6:09 ` Paul Jackson
2003-09-25  6:23 ` William Lee Irwin III
2003-09-25  6:38 ` Paul Jackson
2003-09-25  6:44 ` William Lee Irwin III
2003-09-25  6:51 ` Paul Jackson
2003-09-25  6:59 ` William Lee Irwin III
2003-09-25  7:11 ` Paul Jackson
2003-09-25 13:11 ` Hubertus Franke
2003-09-25 13:19 ` Hubertus Franke
2003-09-25 13:21 ` Hubertus Franke
2003-09-25 13:26 ` Simon Derr
2003-09-25 16:50 ` Dave Hansen
2003-09-25 18:49 ` Luck, Tony [this message]
2003-09-25 20:28 ` Yu, Fenghua
2003-09-26  7:17 ` Sylvain Jeaugey
2003-09-26  7:47 ` Sylvain Jeaugey
2003-09-26 12:57 ` Hubertus Franke
2003-09-26 13:29 ` Hubertus Franke

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=marc-linux-ia64-106451631727404@msgid-missing \
    --to=tony.luck@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    /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