linux-kernel - [V2 for-next PATCH 0/7] workqueue: async idle rebinding and cleanup for hotplug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 17 Sep 2012 23:46:41 +0800
From:	Lai Jiangshan <laijs@...fujitsu.com>
To:	Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org
Cc:	Lai Jiangshan <laijs@...fujitsu.com>
Subject: [V2 for-next PATCH 0/7] workqueue: async idle rebinding and cleanup for hotplug

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/