Matthew wrote:
>
> By adding locking and reference counting, and simplifying the way in which
> sched_domains are created, linked, unlinked and eventually destroyed we
> can use sched_domains as the implementation of cpusets.
I'd be inclined to turn this sideways from what you say.
Rather, add another couple of properties to cpusets:
1) An isolated flag, that guarantees whatever isolation properties
we agree that schedulers, allocators and resource allocators
require between domains, and
2) For those cpusets which are so isolated, the option to add
links of some form, between that cpuset, and distinct scheduler,
allocator and/or resource domains.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.650.933.1373
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
ckrm-tech mailing list
https://lists.sourceforge.net/lists/listinfo/ckrm-tech
