public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Robert Love <rml@tech9.net>
Cc: Andreas Jaeger <aj@suse.de>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] syscall interface for cpu affinity
Date: Sun, 10 Mar 2002 18:45:25 -0500	[thread overview]
Message-ID: <3C8BF015.606BCCDA@mandrakesoft.com> (raw)
In-Reply-To: <1015784104.1261.8.camel@phantasy>  <u8zo1g9nf8.fsf@gromit.moeb> <1015793618.928.17.camel@phantasy>

Robert Love wrote:
> 
> 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 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


Anon!  But there is something uber-ugly about constantly jamming more
and more stuff into procfs without thinking or planning long term...  I
vote for the non-procfs approach :)

-- 
Jeff Garzik      | Usenet Rule #2 (John Gilmore): "The Net interprets
Building 1024    | censorship as damage and routes around it."
MandrakeSoft     |

  parent reply	other threads:[~2002-03-10 23:45 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
2002-03-10 23:45     ` Jeff Garzik [this message]
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=3C8BF015.606BCCDA@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=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