From: Tejun Heo <tj@kernel.org>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] workqueue: reuse wq_update_unbound_numa_attrs_buf as temporary attrs
Date: Thu, 4 Jun 2015 10:09:01 +0900 [thread overview]
Message-ID: <20150604010901.GL20091@mtj.duckdns.org> (raw)
In-Reply-To: <1433341792-2017-5-git-send-email-laijs@cn.fujitsu.com>
Hello,
On Wed, Jun 03, 2015 at 10:29:52PM +0800, Lai Jiangshan wrote:
> tmp_attrs in apply_wqattrs_prepare() is just temporary attrs, we can use
> wq_update_unbound_numa_attrs_buf for it like wq_update_unbound_numa();
>
> The wq_update_unbound_numa_attrs_buf is renamed to wq_calc_node_attrs_buf
> since it is used both for apply_wqattrs_prepare() and wq_update_unbound_numa().
>
> The comment for using wq_calc_node_attrs_buf in wq_update_unbound_numa()
> is also moved to the defination of the wq_calc_node_attrs_buf.
>
> This change also avoids frequently alloc/free the tmp_attrs for every
> workqueue when the low level cpumask is being updated.
>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> kernel/workqueue.c | 31 +++++++++++++------------------
> 1 file changed, 13 insertions(+), 18 deletions(-)
>
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index 0c2f819..4a40165 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -295,8 +295,13 @@ module_param_named(power_efficient, wq_power_efficient, bool, 0444);
>
> static bool wq_numa_enabled; /* unbound NUMA affinity enabled */
>
> -/* buf for wq_update_unbound_numa_attrs(), protected by CPU hotplug exclusion */
> -static struct workqueue_attrs *wq_update_unbound_numa_attrs_buf;
> +/*
> + * PL: resulted attrs of wq_calc_node_cpumask() for apply_wqattrs_prepare()
> + * and wq_update_unbound_numa().
> + * We don't wanna alloc/free temporary attrs for each call. Let's preallocate
> + * one with the access protection of wq_pool_mutex.
> + */
> +static struct workqueue_attrs *wq_calc_node_attrs_buf;
>
> static DEFINE_MUTEX(wq_pool_mutex); /* protects pools and workqueues list */
> static DEFINE_SPINLOCK(wq_mayday_lock); /* protects wq->maydays list */
> @@ -3515,7 +3520,7 @@ apply_wqattrs_prepare(struct workqueue_struct *wq,
> const struct workqueue_attrs *attrs)
> {
> struct apply_wqattrs_ctx *ctx;
> - struct workqueue_attrs *new_attrs, *tmp_attrs;
> + struct workqueue_attrs *new_attrs, *tmp_attrs = wq_calc_node_attrs_buf;
Hmm... this actually bothers me a bit. Can we please do something
like the following?
static struct workqueue_attrs *wq_attrs_shared_buf(void)
{
lockdep_assert_held(...);
return __wq_attrs_shared_buf;
}
--
tejun
prev parent reply other threads:[~2015-06-04 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 14:29 [PATCH 0/4 V3] workqueue: avoid creating identical pwqs Lai Jiangshan
2015-06-03 14:29 ` [PATCH 1/4] workqueue: introduce get_pwq_unlocked() Lai Jiangshan
2015-06-04 1:04 ` Tejun Heo
2015-06-03 14:29 ` [PATCH 2/4] workqueue: reuse the current per-node pwq when its attrs are unchanged Lai Jiangshan
2015-06-04 1:05 ` Tejun Heo
2015-06-03 14:29 ` [PATCH 3/4] workqueue: reuse the current default pwq when its attrs unchanged Lai Jiangshan
2015-06-03 14:29 ` [PATCH 4/4] workqueue: reuse wq_update_unbound_numa_attrs_buf as temporary attrs Lai Jiangshan
2015-06-04 1:09 ` 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=20150604010901.GL20091@mtj.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
Powered by JetHome