From: Anton Blanchard <anton@samba.org>
To: Robert Love <rml@tech9.net>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5: task cpu affinity syscalls
Date: Fri, 12 Apr 2002 13:34:55 +1000 [thread overview]
Message-ID: <20020412033454.GA5773@krispykreme> (raw)
In-Reply-To: <1018275443.857.159.camel@phantasy>
> Attached is a resync to 2.5.8-pre2 of my CPU affinity syscalls for 2.5's
> scheduler.
>
> This patch implements two new syscalls:
>
> int sched_setaffinity(pid_t pid, unsigned int len,
> unsigned long *new_mask_ptr)
>
> int sched_getaffinity(pid_t pid, unsigned int *user_len_ptr,
> unsigned long *user_mask_ptr)
Since this isnt 32/64 bit compatible on big endian machines, can you
write some wrapper functions before all the archs implement it
themselves?
Think of 32 bit userspace passing a big endian bitmask into a 64 bit
kernel:
32 bit:
31-0 63-32 95-64 127-96
64 bit:
63-0 127-64
Anton
next prev parent reply other threads:[~2002-04-12 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 14:17 [PATCH] 2.5: task cpu affinity syscalls Robert Love
2002-04-12 3:34 ` Anton Blanchard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 14:23 Aneesh Kumar K.V
2002-04-11 19:00 ` Robert Love
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=20020412033454.GA5773@krispykreme \
--to=anton@samba.org \
--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 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.