On Fri, Feb 25, 2000 at 04:54:02PM -0800, Dimitris Michailidis wrote:
> * adds a new scheduling policy SCHED_IDLE. Processes of this type
> run on CPUs that would otherwise be idle. Useful for apps like
> SETI@Home, code crackers, etc. Implementation of this feature is
> extremely lightweight. Among the scheduling functions only
> schedule() is SCHED_IDLE-aware and the overhead for non-idle CPUs
> is at most 1 instruction per schedule() invocation;
what happens of something SCHED_IDLE holds a lock and never gets an
CPU time?
> * implements process pinning, which allows a process to be pinned
> to a subset of the CPUs.
IRIX has an API for this -- I would suggest we use that API if
possible.
-cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 29 2000 - 21:00:14 EST