From: Dave Hansen <haveblue@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lse-tech] Re: CPUSET Proposal
Date: Thu, 25 Sep 2003 16:50:53 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106450912817595@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106444308519469@msgid-missing>
On Thu, 2003-09-25 at 06:26, Simon Derr wrote:
> On Wed, 24 Sep 2003, David Mosberger wrote:
>
> > BTW: What do cpusets provide that couldn't be done with user-level
> > tools on top of the existing sched_setaffinity() system call?
> This is a question we had a long in-house debate about.
>
> The main reason of the inclusion of cpusets *inside* the kernel, is that
> we have to deal with applications that may call sched_setaffinity() to
> bind their processes to CPUs. Therefore we have to intercept these calls.
> We could try to do some LD_PRELOAD userland trick or modify the libc, but
> that would not work for statically linked programs.
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.
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2003-09-25 16:50 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 [this message]
2003-09-25 18:49 ` Luck, Tony
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-106450912817595@msgid-missing \
--to=haveblue@us.ibm.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