From: Andreas Jaeger <aj@suse.de>
To: Robert Love <rml@tech9.net>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] syscall interface for cpu affinity
Date: Sun, 10 Mar 2002 21:29:31 +0100 [thread overview]
Message-ID: <u8zo1g9nf8.fsf@gromit.moeb> (raw)
In-Reply-To: <1015784104.1261.8.camel@phantasy>
In-Reply-To: <1015784104.1261.8.camel@phantasy> (Robert Love's message of "10 Mar 2002 13:15:03 -0500")
Robert Love <rml@tech9.net> writes:
> Linus,
>
> I have updated the patch a bit and resycned to 2.5.6. Are you
> interested? I believe a user interface for setting task CPU affinity is
> useful and completes the rest of our sched_* syscalls. A syscall
> implementation seems to be what everyone wants (I have a proc-interface,
> too...)
Please add the procinterface also! I've found it today (for 2.4.18)
and it's much easier to use with existing programs.
Andreas
> This patch implements
>
> int sched_set_affinity(pid_t pid, unsigned int len,
> unsigned long *new_mask_ptr);
>
> int sched_get_affinity(pid_t pid, unsigned int *user_len_ptr,
> unsigned long *user_mask_ptr)
>
> which set and get the cpu affinity (task->cpus_allowed) for a task,
> using the set_cpus_allowed function in Ingo's scheduler. The functions
> properly support changes to cpus_allowed, implement security, and are
> well-tested.
>
> They are based on Ingo's older affinity syscall patch and my older
> affinity proc patch.
>
> Comments?
Please add it for all archs - this is not only interesting for x86,
Andreas
[...]
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2002-03-10 20:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 18:15 [PATCH] syscall interface for cpu affinity Robert Love
2002-03-10 20:29 ` Andreas Jaeger [this message]
2002-03-10 20:53 ` Robert Love
2002-03-10 21:03 ` Andreas Jaeger
2002-03-10 22:23 ` Andreas Schwab
2002-03-10 23:56 ` Andreas Ferber
2002-03-10 23:45 ` Jeff Garzik
1976-03-03 15:58 ` Tim Hockin
2002-03-11 0:08 ` Jeff Garzik
2002-03-11 0:32 ` Tim Hockin
2002-03-10 22:05 ` Chris Wedgwood
2002-03-10 22:11 ` Robert Love
2002-03-11 0:38 ` Andreas Ferber
2002-03-15 22:06 ` Stephen Samuel
2002-03-16 0:43 ` Andreas Ferber
2002-03-16 4:24 ` Stephen Samuel
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=u8zo1g9nf8.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.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