From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
To: Andreas Jaeger <aj@suse.de>
Cc: Robert Love <rml@tech9.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] syscall interface for cpu affinity
Date: Mon, 11 Mar 2002 00:56:19 +0100 [thread overview]
Message-ID: <20020311005619.A1481@devcon.net> (raw)
In-Reply-To: <1015784104.1261.8.camel@phantasy> <u8zo1g9nf8.fsf@gromit.moeb> <1015793618.928.17.camel@phantasy> <u8bsdw9lvd.fsf@gromit.moeb>
In-Reply-To: <u8bsdw9lvd.fsf@gromit.moeb>; from aj@suse.de on Sun, Mar 10, 2002 at 10:03:02PM +0100
On Sun, Mar 10, 2002 at 10:03:02PM +0100, Andreas Jaeger wrote:
> >
> > 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 ;-)
$ (set_affinity 1; program arguments...)
set_affinity just calls sched_set_affinity(getppid()), and everything
is fine (and even shorter to type) :-)
Andreas
--
Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG
---------------------------------------------------------
+49 521 1365800 - af@devcon.net - www.devcon.net
next prev parent reply other threads:[~2002-03-10 23:56 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
2002-03-10 22:23 ` Andreas Schwab
2002-03-10 23:56 ` Andreas Ferber [this message]
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=20020311005619.A1481@devcon.net \
--to=aferber@techfak.uni-bielefeld.de \
--cc=aj@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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