Re: [PATCH] Process pinning

2001-04-17 Thread Albert D. Cahalan
Nick Pollitt writes: > Changes to array.c expose cpus_allowed in proc/pid/stat. ... > -%lu %lu %lu %lu %lu %lu %lu %lu %d %d\n", > +%lu %lu %lu %lu %lu %lu %lu %lu %d %d %lu\n", ... > - task->processor); > + task->processor, > + task->cpus_allowed); This isn

Re: [PATCH] Process pinning

2001-04-17 Thread Andrew Morton
Tim Hockin wrote: > > > disallowed CPU on which it is already running. And even a non-RT > > process will stick on its disallowed CPU as long as nothing else runs > > there. > > are we going to keep the cpus_allowed API? If we want the (IMHO) more > flexible sysmp() API - I'll finish the 2.4 p

Re: [PATCH] Process pinning

2001-04-17 Thread Tim Hockin
> disallowed CPU on which it is already running. And even a non-RT > process will stick on its disallowed CPU as long as nothing else runs > there. are we going to keep the cpus_allowed API? If we want the (IMHO) more flexible sysmp() API - I'll finish the 2.4 port. If we are going to keep cpu

Re: [PATCH] Process pinning

2001-04-17 Thread Rusty Russell
In message <[EMAIL PROTECTED]> you write: > Changes to array.c expose cpus_allowed in proc/pid/stat. Call me old fashioned, but I prefer my bitmasks in hex. Please also consider changing: still_running: c = goodness(prev, this_cpu, prev->active_mm); next = prev; to: still_ru

[PATCH] Process pinning

2001-04-09 Thread Nick Pollitt
This patch applies cleanly to 2.4.3-ac3. Changes to array.c expose cpus_allowed in proc/pid/stat. PR_GET_RUNON and PR_SET_RUNON were done by Ingo and Dimitris. Added MUSTRUN_PID and RUNANY_PID. Also attached is runon and it's manpage. Nick diff -X /home/npollitt/dontdiff -Nur 243-ac3/l