From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
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 3/3 V8] workqueue: Allow modifying low level unbound workqueue cpumask
Date: Tue, 28 Apr 2015 09:44:44 +0800 [thread overview]
Message-ID: <553EE60C.1040503@cn.fujitsu.com> (raw)
In-Reply-To: <20150427160756.GE1499@htj.duckdns.org>
Hello
>
>> --- a/include/linux/workqueue.h
>> +++ b/include/linux/workqueue.h
>> @@ -424,6 +424,7 @@ struct workqueue_attrs *alloc_workqueue_attrs(gfp_t gfp_mask);
>> void free_workqueue_attrs(struct workqueue_attrs *attrs);
>> int apply_workqueue_attrs(struct workqueue_struct *wq,
>> const struct workqueue_attrs *attrs);
>> +int workqueue_set_unbound_cpumask(cpumask_var_t cpumask);
>
> Why is this a public function?
In V4 patchset, Kevin Hilman had requested the wq_unbound_cpumask
to be "cpumask_complement(wq_unbound_cpumask, tick_nohz_full_mask);"
I replied against it and I suggested that wq_unbound_cpumask can be
re-set after workqueue initialized it.
And Frederic Weisbecker seemed on my side:
"""
If it should be the default on NO_HZ_FULL, maybe we should do this from the
tick nohz code. Some late or fs initcall that will do the workqueue affinity,
timer affinity, etc...
"""
So, we need an API to modify the wq_unbound_cpumask, and I provided
this public function. Otherwise, the other code can't modify it.
>
>> --- a/kernel/workqueue.c
>> +++ b/kernel/workqueue.c
>> @@ -3548,13 +3549,18 @@ apply_wqattrs_prepare(struct workqueue_struct *wq,
>> * If something goes wrong during CPU up/down, we'll fall back to
>> * the default pwq covering whole @attrs->cpumask. Always create
>> * it even if we don't use it immediately.
>> + *
>> + * If the user configured cpumask doesn't overlap with the
>> + * wq_unbound_cpumask, we fallback to the wq_unbound_cpumask.
>> */
>> + if (unlikely(cpumask_empty(new_attrs->cpumask)))
>> + cpumask_copy(new_attrs->cpumask, wq_unbound_cpumask);
>
> Please see below.
>
>> ctx->dfl_pwq = alloc_unbound_pwq(wq, new_attrs);
>> if (!ctx->dfl_pwq)
>> goto out_free;
>>
>> for_each_node(node) {
>> - if (wq_calc_node_cpumask(attrs, node, -1, tmp_attrs->cpumask)) {
>> + if (wq_calc_node_cpumask(new_attrs, node, -1, tmp_attrs->cpumask)) {
>> ctx->pwq_tbl[node] = alloc_unbound_pwq(wq, tmp_attrs);
>> if (!ctx->pwq_tbl[node])
>> goto out_free;
>> @@ -3564,7 +3570,10 @@ apply_wqattrs_prepare(struct workqueue_struct *wq,
>> }
>> }
>>
>> + /* save the user configured attrs */
>> + cpumask_and(new_attrs->cpumask, attrs->cpumask, cpu_possible_mask);
>
> Wouldn't this make a lot more sense above when copying @attrs into
> @new_attrs? The comment there even says "make a copy of @attrs and
> sanitize it". Copy to @new_attrs, mask with wq_unbound_cpumask and
> fall back to wq_unbound_cpumask if empty.
It should be:
+ copy_workqueue_attrs(new_attrs, attrs);
+ cpumask_and(new_attrs->cpumask, new_attrs->cpumask, cpu_possible_mask);
>
>> +static int workqueue_apply_unbound_cpumask(void)
>> +{
> ...
>> + list_for_each_entry_safe(ctx, n, &ctxs, list) {
>
> Is the following list_del() necessary? The list is never used again,
> right?
It isn't necessary. It was added in V7. I thought it could make
the code more normal.
Thanks
Lai
next prev parent reply other threads:[~2015-04-28 2:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 9:58 [PATCH 0/3 V8] workqueue: Introduce low-level unbound wq sysfs cpumask Lai Jiangshan
2015-04-27 9:58 ` [PATCH 1/3 V8] workqueue: split apply_workqueue_attrs() into 3 stages Lai Jiangshan
2015-04-27 9:58 ` [PATCH 2/3 V8] workqueue: Create low-level unbound workqueues cpumask Lai Jiangshan
2015-04-27 15:45 ` Tejun Heo
2015-04-27 9:58 ` [PATCH 3/3 V8] workqueue: Allow modifying low level unbound workqueue cpumask Lai Jiangshan
2015-04-27 16:07 ` Tejun Heo
2015-04-28 1:44 ` Lai Jiangshan [this message]
2015-04-28 2:24 ` Lai Jiangshan
2015-04-28 3:49 ` Tejun Heo
2015-04-28 10:16 ` Lai Jiangshan
2015-04-30 9:23 ` Lai Jiangshan
2015-04-28 3:44 ` Tejun Heo
2015-04-28 4:36 ` Mike Galbraith
2015-04-28 10:31 ` Lai Jiangshan
2015-04-28 12:15 ` Mike Galbraith
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=553EE60C.1040503@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=bitbucket@online.de \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tj@kernel.org \
--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