public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Chris Wedgwood <cw@f00f.org>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] syscall interface for cpu affinity
Date: 10 Mar 2002 17:11:28 -0500	[thread overview]
Message-ID: <1015798309.928.21.camel@phantasy> (raw)
In-Reply-To: <20020310220557.GA12383@tapu.f00f.org>
In-Reply-To: <1015784104.1261.8.camel@phantasy>  <20020310220557.GA12383@tapu.f00f.org>

On Sun, 2002-03-10 at 17:05, Chris Wedgwood wrote:

> Can't wer just copy the IRIX interface here as some other pathces have
> in the past?

Is that psets?  If so, no thanks.

I want a simple, clean, quick implementation.  I have seen patches that
do a lot more than what my simple implementation does, and that really
does not interest me and I suspect Ingo and others feel the same way. 
Setting a simple per-task bitmask that is inherited is all we need.

Linux scheduler API is already our own standard.  I'd rather support
that (i.e. add another simple sched_* call) than some evil other
interface - but that is just me.

	Robert Love


  reply	other threads:[~2002-03-10 22:12 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
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 [this message]
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=1015798309.928.21.camel@phantasy \
    --to=rml@tech9.net \
    --cc=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --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