> BTW: What do cpusets provide that couldn't be done with user-level > tools on top of the existing sched_setaffinity() system call? I don't see how you can do the migrate_cpuset_processes() from a user level daemon. Just because two tasks happen to be allowed on the same CPUs doesn't mean they are in the same cpuset. The kernel must track, across forks, which tasks share a given cpuset. There are also some resource management capabilities, such as tracking and controlling how much memory a cpuset takes, and swapping (with possible oom kill) against a cpuset that one can consider extending this to, but only if it's in the kernel. But I'm not ready to push this point ... yet. And the permission model has to remain a rather primitive "root can do anything, anyone else can just subset their parent" if it lacks kernel hooks to track uid/suid ownership of each cpuset. -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.650.933.1373 - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Thu Sep 25 01:41:19 2003
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:17 EST