Messages in this thread | | | Date | Sat, 24 Sep 2011 12:07:18 +0900 | From | Tejun Heo <> | Subject | Re: [PATCH] workqueue: Restore cpus_allowed mask for sleeping workqueue rescue threads |
| |
Hello,
On Sun, Sep 18, 2011 at 09:36:57AM +0300, Gilad Ben-Yossef wrote: > There is at least one use case where I think this can be a problem - > cpu isolation. > > If you decide to partition your CPU to give some group of processes a > set of CPUs all to their own (using cgroups/cpuset for example) having > non related bound processes really gets in the way. You would really > want to migrate away non related tasks from the isolated cpuset and > having a bound kernel thread prevents that.
Hmm... I don't think this has much to do with CPU isolation. Workqueue rescuers are reactively invoked to resolve possible resource deadlock. It doesn't initiate operations on itself while CPU isolation requires moving all sources of unwanted activites off the isolated CPUs. Having idle rescuers not bound to any CPU might look prettier but wouldn't help anything - it's not an activity source and the 'wanted' activities on the isolated CPU also require rescuers for forward progress guarantee.
Thanks.
-- tejun
| |