Hmmm, AFAICS, sched_getaffinity() and sched_setaffinity()
allow the calling process to be bound to the nominated CPU(s), but that is not
the same as giving them exclusive access, is it? In other words, other
processes which have no particualr affinity needs can presumably still be
scheduled to run on the same processor.
I am looking for something more akin to the patch I referred to...or did I miss
something in the effect of set_cpus_allowed()?
Thanks for the replies, Shaheed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Apr 15 2003 - 22:00:27 EST