Re: [PATCH 4/4] workqueue: Allow modifying low level unbound workqueue cpumask

[Christoph Lameter]

On Thu, 12 Mar 2015, Lai Jiangshan wrote:

> The per-nodes' pwqs are mandatorily controlled by the low level cpumask, while
> the default pwq ignores the low level cpumask when (and ONLY when) the cpumask set
> by the user doesn't overlap with the low level cpumask. In this case, we can't
> apply the empty cpumask to the default pwq, so we use the user-set cpumask
> directly.

I am wondering now why we have two cpumasks? A script can just interate
through the work queues if we want to set them all right? Then we do not
have to deal with the conflict between the settings in the kernel.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/