From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: <linux-kernel@vger.kernel.org>
Cc: Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 4/7 V2] workqueue: reuse the current per-node pwq when its attrs unchanged
Date: Mon, 25 May 2015 17:47:17 +0800 [thread overview]
Message-ID: <5562EFA5.2030706@cn.fujitsu.com> (raw)
In-Reply-To: <1431433955-3173-5-git-send-email-laijs@cn.fujitsu.com>
Hi, TJ
The patch 4/5/6 does reduce cpu and temporary-memory usage sometimes.
But it is in slow path where small optimization is commonly unwelcome at.
Do I need to refactor the patches? I'm in doubt for the necessary.
Thanks,
Lai
next prev parent reply other threads:[~2015-05-25 9:44 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
2015-05-25 9:47 ` Lai Jiangshan [this message]
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=5562EFA5.2030706@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.