mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/7 V2] workqueue: reuse the current per-node pwq when its attrs unchanged
Date: Mon, 18 May 2015 16:34:31 -0400	[thread overview]
Message-ID: <20150518203431.GE24861@htj.duckdns.org> (raw)
In-Reply-To: <1431433955-3173-5-git-send-email-laijs@cn.fujitsu.com>

On Tue, May 12, 2015 at 08:32:32PM +0800, Lai Jiangshan wrote:
> If the cpuamsk is changed, it is possible that only a part of the per-node

         cpumask

> pwq is affected.  This can happen when the user changes the cpumask of
> a workqueue or the low level cpumask.
> 
> So we try to reuse the current per-node pwq when its attrs unchanged.

                                                             are unchanged.

> @@ -3592,9 +3593,14 @@ apply_wqattrs_prepare(struct workqueue_struct *wq,
>  
>  	for_each_node(node) {
>  		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])
> +			pwq = unbound_pwq_by_node(wq, node);
> +			if (pwq && wqattrs_equal(tmp_attrs, pwq->pool->attrs))
> +				pwq = get_pwq_unlocked(pwq);

Ah, okay, the function gets used here again.  BTW, why does this
function return anything?  Can this function ever return something
which isn't the pwq it was called with?

> +			else
> +				pwq = alloc_unbound_pwq(wq, tmp_attrs);
> +			if (!pwq)
>  				goto out_free;

If get_pwq_unlocked() can't fail, why are we testing for NULL pwq
here?  This code is kinda misleading.

> +			ctx->pwq_tbl[node] = pwq;
>  		} else {
>  			ctx->dfl_pwq->refcnt++;
>  			ctx->pwq_tbl[node] = ctx->dfl_pwq;
> @@ -3739,7 +3745,6 @@ static void wq_update_unbound_numa(struct workqueue_struct *wq, int cpu,
>  	cpumask = target_attrs->cpumask;
>  
>  	copy_workqueue_attrs(target_attrs, wq->unbound_attrs);
> -	pwq = unbound_pwq_by_node(wq, node);
>  
>  	/*
>  	 * Let's determine what needs to be done.  If the target cpumask is
> @@ -3748,6 +3753,7 @@ static void wq_update_unbound_numa(struct workqueue_struct *wq, int cpu,
>  	 * equals the default pwq's, the default pwq should be used.
>  	 */
>  	if (wq_calc_node_cpumask(wq->dfl_pwq->pool->attrs, node, cpu_off, cpumask)) {
> +		pwq = unbound_pwq_by_node(wq, node);

It'd be nice to note this change in the patch description.

Thanks.

-- 
tejun

  reply	other threads:[~2015-05-18 20:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 12:32 [PATCH 0/7 V2] workqueue: cleanup for attr management Lai Jiangshan
2015-05-12 12:32 ` [PATCH 1/7 V2] workqueue: wq_pool_mutex protects the attrs-installation Lai Jiangshan
2015-05-12 12:32 ` [PATCH 2/7 V2] workqueue: simplify wq_update_unbound_numa() Lai Jiangshan
2015-05-18 20:21   ` Tejun Heo
2015-05-12 12:32 ` [PATCH 3/7 V2] workqueue: introduce get_pwq_unlocked() Lai Jiangshan
2015-05-18 20:28   ` Tejun Heo
2015-05-18 20:41   ` Tejun Heo
2015-05-12 12:32 ` [PATCH 4/7 V2] workqueue: reuse the current per-node pwq when its attrs unchanged Lai Jiangshan
2015-05-18 20:34   ` Tejun Heo [this message]
2015-05-25  9:47   ` Lai Jiangshan
2015-05-26 18:51     ` Tejun Heo
2015-05-12 12:32 ` [PATCH 5/7 V2] workqueue: reuse the current default " Lai Jiangshan
2015-05-18 20:38   ` Tejun Heo
2015-05-12 12:32 ` [PATCH 6/7 V2] workqueue: reuse wq_update_unbound_numa_attrs_buf as temporary attrs Lai Jiangshan
2015-05-12 12:32 ` [PATCH 7/7 V2] workqueue: add get_node_unbound_pwq() Lai Jiangshan
2015-05-18  0:39 ` [PATCH 0/7 V2] workqueue: cleanup for attr management Lai Jiangshan
2015-05-18  1:26   ` Tejun Heo
2015-05-18  2:06     ` Lai Jiangshan

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=20150518203431.GE24861@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.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®