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 22:03:02 +0100 [thread overview]
Message-ID: <u8bsdw9lvd.fsf@gromit.moeb> (raw)
In-Reply-To: <1015784104.1261.8.camel@phantasy> <u8zo1g9nf8.fsf@gromit.moeb> <1015793618.928.17.camel@phantasy>
In-Reply-To: <1015793618.928.17.camel@phantasy> (Robert Love's message of "10 Mar 2002 15:53:38 -0500")
Robert Love <rml@tech9.net> writes:
> On Sun, 2002-03-10 at 15:29, Andreas Jaeger wrote:
>
>> Please add the procinterface also! I've found it today (for 2.4.18)
>> and it's much easier to use with existing programs.
>
> I agree and I really like the proc-interface. There is something uber
> cool about:
>
> cat 1 > /proc/pid/affinity
I agree.
> I have a patch for 2.5.6 for proc-based affinity interface here:
>
> http://www.kernel.org/pub/linux/kernel/people/rml/cpu-affinity/v2.5/cpu-affinity-proc-rml-2.5.6-1.patch
>
> I suspect, however, that despite both patches being small we really only
> want to pick and standardize on one. The syscall interface has two main
> things going for it against a proc-based implementation: it is faster
> and /proc may not be mounted. The masses have spoken on this issue.
>
> Note you can use the syscall interface with existing programs, too.
> Just write a program to take in a pid and mask and call
> sched_set_affinity.
What I need at the moment is a wrapper - and you can do it two ways:
$ run_with_affinity 1 program arguments...
$ (cat 1 > /proc/self/affinity; program arguments...)
The second one is much easier coded ;-)
>> Please add it for all archs - this is not only interesting for x86,
>
> I'll send Linus the patch for other arches if/when he accepts this patch
> - I have no problem with that.
Thanks,
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 21:03 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
2002-03-10 20:53 ` Robert Love
2002-03-10 21:03 ` Andreas Jaeger [this message]
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=u8bsdw9lvd.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