From: Tejun Heo <tj@kernel.org>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: Ripduman Sohan <Ripduman.Sohan@cl.cam.ac.uk>,
linux-kernel@vger.kernel.org, peterz@infradead.org
Subject: Re: [PATCH] workqueue: Restore cpus_allowed mask for sleeping workqueue rescue threads
Date: Sat, 24 Sep 2011 12:07:18 +0900 [thread overview]
Message-ID: <20110924030718.GA29319@htj.dyndns.org> (raw)
In-Reply-To: <CAOtvUMf0Dx04Piw8bx2oD+F9ttiBP_xCpin7fTvoQqs_dn=ZRQ@mail.gmail.com>
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
next prev parent reply other threads:[~2011-09-24 3:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 13:36 [PATCH] workqueue: Restore cpus_allowed mask for sleeping workqueue rescue threads Ripduman Sohan
2011-09-02 0:29 ` Tejun Heo
2011-09-15 16:14 ` Ripduman Sohan
2011-09-17 0:29 ` Tejun Heo
2011-09-18 6:36 ` Gilad Ben-Yossef
2011-09-24 3:07 ` Tejun Heo [this message]
2011-09-25 6:02 ` Gilad Ben-Yossef
2011-09-30 8:09 ` Tejun Heo
2011-09-30 8:54 ` Ripduman Sohan
2011-09-30 8:57 ` Tejun Heo
2011-09-30 8:59 ` Ripduman Sohan
2011-10-01 1:10 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2011-08-31 13:17 Ripduman Sohan
2011-08-31 15:20 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110924030718.GA29319@htj.dyndns.org \
--to=tj@kernel.org \
--cc=Ripduman.Sohan@cl.cam.ac.uk \
--cc=gilad@benyossef.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.