From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>, linux-kernel@vger.kernel.org
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: [V2 for-next PATCH 0/7] workqueue: async idle rebinding and cleanup for hotplug
Date: Mon, 17 Sep 2012 23:46:41 +0800 [thread overview]
Message-ID: <1347896808-2398-1-git-send-email-laijs@cn.fujitsu.com> (raw)
Patch1 fix new found possible bug.
Patch2 use async algorithm to replace the synchronous algorithm to rebind
idle workers.
The synchronous algorithm requires 3 hand shakes, it introduces much
complicated.
The new async algorithm does not do any synchronization. it removes
the idle workers from idle_list to ensure the local-wake-up is correct
instead.
Patch3-7 do simple cleanup
Patch2-7 are ready for for-next. I have other devlopment and cleanup for workqueue,
should I wait this patchset merged or send them at the same time?
Lai Jiangshan (7):
workqueue: clear WORKER_REBIND unconditionaly in
busy_worker_rebind_fn()
workqueue: async idle rebinding
workqueue: new day don't need WORKER_REBIND for busy rebinding
workqueue: remove WORKER_REBIND
workqueue: rename manager_mutex to assoc_mutex
workqueue: use __cpuinit instead of __devinit for cpu callback
workqueue: use hotcpu_notifier() for workqueue_cpu_down_callback()
kernel/workqueue.c | 228 ++++++++++++++++++---------------------------------
1 files changed, 81 insertions(+), 147 deletions(-)
--
1.7.4.4
next reply other threads:[~2012-09-17 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 15:46 Lai Jiangshan [this message]
2012-09-17 15:46 ` [V2 for-3.6-fixes PATCH 1/7] workqueue: clear WORKER_REBIND unconditionaly in busy_worker_rebind_fn() Lai Jiangshan
2012-09-17 15:46 ` [V2 for-next PATCH 2/7] workqueue: async idle rebinding Lai Jiangshan
2012-09-17 15:46 ` [V2 for-next PATCH 3/7] workqueue: new day don't need WORKER_REBIND for busy rebinding Lai Jiangshan
2012-09-17 15:46 ` [V2 for-next PATCH 4/7] workqueue: remove WORKER_REBIND Lai Jiangshan
2012-09-17 15:46 ` [V2 for-next PATCH 5/7] workqueue: rename manager_mutex to assoc_mutex Lai Jiangshan
2012-09-17 15:46 ` [V2 for-next PATCH 6/7] workqueue: use __cpuinit instead of __devinit for cpu callback Lai Jiangshan
2012-09-17 15:46 ` [V2 for-next PATCH 7/7] workqueue: use hotcpu_notifier() for workqueue_cpu_down_callback() Lai Jiangshan
2012-09-18 9:40 ` [V2 for-next PATCH 0/7] workqueue: async idle rebinding and cleanup for hotplug Lai Jiangshan
2012-09-18 17:03 ` 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=1347896808-2398-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
all inboxes | Powered by JetHome®