* Peter Zijlstra <a.p.zijlstra@chel...> wrote:

> My vision on the direction we should take wrt cpu isolation.
>
> Next on the list would be figuring out a nice solution to the
> workqueue flush issue.

nice work Peter, i find this "system sets" extension to cpusets a much
more elegant (and much more future-proof) solution than the proposed
spreadout of the limited hack of isolcpus/cpu_isolated_map. It
concentrates us on a single API and on a single mechanism to handle
isolation matters. (be that for clustering/supercomputing or real-time
purposes)

Thanks for insisting on using cpusets for this!

i've queued up your patches in sched-devel.git, and lets make sure this
has no side-effects on existing functionality. (it shouldnt)

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger...
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/