All of lore.kernel.org
 help / color / mirror / Atom feed
From: P@draigBrady.com
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: proper API for sched_setaffinity ?
Date: Thu, 26 May 2005 10:02:34 +0100	[thread overview]
Message-ID: <429590AA.8080505@draigBrady.com> (raw)
In-Reply-To: <4294BAD8.4030300@nortel.com>

Chris Friesen wrote:
> On my system (Mandrake 10.0) the man page for sched_setaffinity() lists 
> the prototype as:
> 
> int  sched_setaffinity(pid_t  pid,  unsigned  int  len,  unsigned  long
>        *mask);
> 
> 
> But /usr/include/sched.h gives it as
> 
> extern int sched_setaffinity (__pid_t __pid, __const cpu_set_t *__mask)
> 
> Which is correct?

The sched_setaffinity interface really is very messy:
http://mail.linux.ie/pipermail/ilug/2004-November/019784.html
API changes in same minor version of glibc should just not happen.

-- 
Pádraig Brady - http://www.pixelbeat.org
--

      parent reply	other threads:[~2005-05-26  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 17:50 proper API for sched_setaffinity ? Chris Friesen
2005-05-25 18:26 ` Christoph Hellwig
2005-05-25 18:33 ` Sergey Vlasov
2005-05-26  9:02 ` P [this message]

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=429590AA.8080505@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.