On Thu, 2004-10-07 at 07:28, Paul Jackson wrote: > Rick wrote: > > * There is no clear policy on how to amiably create an exclusive set. > > The main problem is what to do with the tasks already there. > > There is a policy, that works well, and those of us in this business > have been using for years. When the system boots, you put everything > that doesn't need to be pinned elsewhere in a bootcpuset, and leave > the rest of the system dark. You then, whether by manual administrative > techniques or a batch scheduler, hand out dedicated sets of CPU and > Memory to jobs, which get exclusive use of those compute resources > (or controlled sharing with only what you intentionally let share).
No one is trying to take that away. There is nothing that says you can't boot with a small, 1-2 CPU 'boot' domain where you stick all those tasks you typically put in a 'boot' cpuset. <offtopic> In fact, people have talked before about reducing boot times by booting only a single CPU, then bringing the rest online later. This work could potentially facilitate that. Boot up just a single 'boot' CPU. All 'boot' tasks would necessarily be stuck there. Create a new 'work' domain and add (hotplug on) CPUs into that domain to your heart's content. </offtopic> -Matt ------------------------------------------------------- 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
