On Mon, 2015-03-02 at 10:29 -0500, Tejun Heo wrote: > On Mon, Mar 02, 2015 at 01:44:50PM +0100, Mike Galbraith wrote: > > Hm, I'm now all system-disease-ified now (still hate the bloody thing), > > and have no problem isolating cpus via cpusets, modulo workqueues > > wanting a bat upside the head. > > It shouldn't be difficult to teach workqueue pools to follow the same > rules. This matters only for the unbound ones anyway, right? 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. -Mike -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
