Re: [PATCH v4 2/2] cpusets,isolcpus: add file to show isolated cpus in cpuset

From: Tejun Heo
Date: Mon Mar 02 2015 - 11:09:14 EST

On Mon, Mar 02, 2015 at 05:02:57PM +0100, Mike Galbraith wrote:
> Well, those are the only ones we can do anything about. Dirt simple
> diddling of the workqueue default mask as sched domains are
> added/removed should do it I think. Automatically moving any existing
> unbound worker away from isolated cores at the same time would be a
> bonus, most important is that no new threads sneak in.

Worker pools are immutable once created and configuraiton changes are
achieved by creating new pools and draining old ones but at any rate
making it follow config changes is almost trivial. Figuring out
configuration policy might take a bit of effort tho. Can you point me
to what specific configuration it should be following?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at