On Wed, Jan 16, 2013 at 05:42:32PM -0800, Tejun Heo wrote: > Currently, on the backend side, there are two layers of abstraction. > For each CPU and the special unbound wq-specific CPU, there's one > global_cwq. gcwq in turn hosts two worker_pools - one for normal > priority, the other for highpri - each of which actually serves the > work items. > > worker_pool is the later addition to support separate pool of workers > for highpri workqueues. Stuff was moved to worker_pool on as-needed > basis and, as a result, the two pools belonging to the same CPU share > some stuff in the gcwq - most notably the lock and the hash table for > work items currently being executed.
Applied to wq/for-3.9. Thanks! -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
