From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: <linux-kernel@vger.kernel.org>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>, Tejun Heo <tj@kernel.org>
Subject: [PATCH 0/4 V3] workqueue: avoid creating identical pwqs
Date: Wed, 3 Jun 2015 22:29:48 +0800 [thread overview]
Message-ID: <1433341792-2017-1-git-send-email-laijs@cn.fujitsu.com> (raw)
Hi,
In some conditions, the default pwq or the per-node pwq might be rebuilt identically,
it causes overhead. The code of this patchset checks the attrs and avoids it.
Patch1 adds get_pwq_unlocked() due to reusing old pwq in more cases
Patch2~3 avoid to create identical pwqs
Patch4 reuse wq_update_unbound_numa_attrs_buf, simple cleanup
changed from V2:
o get_pwq_unlocked() returns void
o move the check of the return value of alloc_unbound_pwq() into its branch
o wq_update_unbound_numa_attrs_buf is renamed
o kill get_alloc_node_unbound_pwq(), may or may not replement it in future
Cc: Tejun Heo <tj@kernel.org>
Lai Jiangshan (4):
workqueue: introduce get_pwq_unlocked()
workqueue: reuse the current per-node pwq when its attrs are unchanged
workqueue: reuse the current default pwq when its attrs unchanged
workqueue: reuse wq_update_unbound_numa_attrs_buf as temporary attrs
kernel/workqueue.c | 94 ++++++++++++++++++++++++++++++++----------------------
1 file changed, 56 insertions(+), 38 deletions(-)
--
2.1.0
next reply other threads:[~2015-06-03 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 14:29 Lai Jiangshan [this message]
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
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=1433341792-2017-1-git-send-email-laijs@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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