Re: [PATCH] workqueue: respect isolated cpus when queueing an unbound work

[Tejun Heo]

Hello,

On Sat, Oct 21, 2017 at 07:13:33PM +0300, Tal Shorer wrote:
> > Do we have a consistent behavior around this?  Are there different
> > examples where isolcpus interact with other dynamically configurable
> > parameters?
> >
> sched_setaffinity comes to mind, which obviously bypasses isolcpus.
> Running git grep, other uses of cpu_isolated_map are just its
> initialization and its use and the initialization of
> non_isolated_cpus.

Can you add a comment explaining that it's intentional that we only
follow isolcpus during boot and allow later overrides?

Thanks.

-- 
tejun