Re: [patch] sched_[set|get]_affinity() syscall, 2.4.15-pre9

[Joe Korty <l-k@mindspring.com>]

At 09:40 AM 11/27/01 +0100, Ingo Molnar wrote:
> > This patch comes about as an alternative to Ingo Molnar's
> > syscall-implemented version.  Ingo's code is nice; however I and
> > others expressed discontent as yet another syscall. [...]
>
>i do express discontent over yet another procfs bloat. What if procfs is
>not mounted in a high security installation? Are affinities suddenly
>unavailable? Such kind of dependencies are unacceptable IMO - if we want
>to export the setting of affinities to user-space, then it should be a
>system call.

...

> > [...] Other benefits include the ease with which to set the affinity
> > of tasks that are unaware of the new interface [...]


I have not yet seen the patch, but one nice feature that a system call 
interface
could provide is the ability to *atomically* change the cpu affinities of 
sets of
processes -- for example, all processes with a certain uid or gid.  All that
would be required would be for the system call to accept a command integer
value which would define what the argument integer value would mean -- a pid,
a gid, or a uid.

Joe