On Wed, 4 Jun 2008, Paul Jackson wrote:

quoted text
> > That would identify both kthreads that have been created with a subsequent 
> > call to set_cpus_allowed() or kthread_bind().
> 
> Or do I misunderstand?
> 
> If I am reading you correctly, then would it work to have a check in the
> cpuset code (rather than in the lower set_cpus_allowed() routine),
> where that check refused to move tasks out of the root cpuset if they
> were (1) kernel threads (mm NULL) and (2) had cpus_allowed that were a
> strict subset of the root cpusets 'cpus' (the online cpus).
> 

No, because sched_setaffinity() can still move the threads.
--
unsubscribe notice
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/