On Tue, May 20, 2014 at 05:46:26PM +0800, Lai Jiangshan wrote: > Patch1-4: async worker destruction > > Patch2 reduces the review burden. It will be easier to review the whole > patchset if we know destroy_worker() is forced to destroy idle workers only. > > Patch5-10: worker attaching/detaching and simplify the workers management > > The code which attaches a worker to the pool and detaches a worker from the > pool > is unfolded in create_worker()/destroy_worker(). > The patchset moves this attaching/detaching code out and wraps them. > > patch3-4 moves the detaching code out from destroy_worker(), and make > manger_mutex only protects the detaching code only rather than > protects the whole worker-destruction path. > > patch5-7 makes manger_mutex only protects the attaching code rather than the > whole worker-creation path. > > patch8: rename manger_mutex to attach_mutex > patch9-10: moves the attaching code out from create_worker() and use it for > rescuer. > > > Lai Jiangshan (10): > workqueue: use manager lock only to protect worker_idr > workqueue: destroy_worker() should destroy idle workers only > workqueue: async worker destruction > workqueue: destroy worker directly in the idle timeout handler > workqueue: separate iteration role from worker_idr > workqueue: convert worker_idr to worker_ida > workqueue: narrow the protection range of manager_mutex > workqueue: rename manager_mutex to attach_mutex > workqueue: separate pool-attaching code out from create_worker() > workqueue: use generic attach/detach routine for rescuers
Applied to wq/for-3.16 with comment and description updates. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
