From: Tejun Heo <tj@kernel.org>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, Christoph Lameter <cl@linux.com>,
Kevin Hilman <khilman@linaro.org>,
Mike Galbraith <bitbucket@online.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH V9] workqueue: Allow modifying low level unbound workqueue cpumask
Date: Thu, 30 Apr 2015 09:29:39 -0400 [thread overview]
Message-ID: <20150430132939.GA1949@htj.duckdns.org> (raw)
In-Reply-To: <1430385372-3351-1-git-send-email-laijs@cn.fujitsu.com>
On Thu, Apr 30, 2015 at 05:16:12PM +0800, Lai Jiangshan wrote:
> Allow to modify the low-level unbound workqueues cpumask through
> sysfs. This is performed by traversing the entire workqueue list
> and calling apply_wqattrs_prepare() on the unbound workqueues
> with the new low level mask. Only after all the preparation are done,
> we commit them all together.
>
> Ordered workqueues are ignored from the low level unbound workqueue
> cpumask, it will be handled in near future.
>
> All the (default & per-node) pwqs are mandatorily controlled by
> the low level cpumask. If the user configured cpumask doesn't overlap
> with the low level cpumask, the low level cpumask will be used for the
> wq instead.
>
> The comment of wq_calc_node_cpumask() is updated and explicitly
> requires that its first argument should be the attrs of the default
> pwq.
>
> The default wq_unbound_cpumask is cpu_possible_mask. The workqueue
> subsystem doesn't know its best default value, let the system manager
> or the other subsystem set it when needed.
>
> Changed from V8:
> merge the calculating code for the attrs of the default pwq together.
> minor change the code&comments for saving the user configured attrs.
> remove unnecessary list_del().
> minor update the comment of wq_calc_node_cpumask().
> update the comment of workqueue_set_unbound_cpumask();
>
> Cc: Christoph Lameter <cl@linux.com>
> Cc: Kevin Hilman <khilman@linaro.org>
> Cc: Lai Jiangshan <laijs@cn.fujitsu.com>
> Cc: Mike Galbraith <bitbucket@online.de>
> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Original-patch-by: Frederic Weisbecker <fweisbec@gmail.com>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
Applied to wq/for-4.2 and yeah the prepare function looks better now.
Thanks a lot for the persistence.
--
tejun
prev parent reply other threads:[~2015-04-30 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 9:16 Lai Jiangshan
2015-04-30 13:29 ` Tejun Heo [this message]
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=20150430132939.GA1949@htj.duckdns.org \
--to=tj@kernel.org \
--cc=bitbucket@online.de \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=khilman@linaro.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®