> Martin wrote: >> (and existing processes forcibly migrated off) > > No can do. As described in my previous message, everything is happily > moved already, with some user code (and a CPU_MASK_ALL patch to kthread > I haven't submitted yet) _except_ for a few per-CPU threads such as the > migration helpers, which can _not_ be moved off their respective CPUs.
Well, that just means we need to check for things bound to a subset when we fork it off. ie if we have cpus 1,2,3,4 ... and there is A bound to 1 B bound to 2 C bound to 3 D bound to 4 Then when I fork off exclusive subset for CPUs 1&2, I have to push A & B into it. You're right, what I said was broken ... but it doesn't seem hard to fix. M. ------------------------------------------------------- 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
