Hello, 2011/6/18 Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>: > For my education, what is the benefit of creating a dedicated workqueue > with alloc_workqueue (which, as far as I understand, does not end up > having dedicated worker threads but will use the common pool) and simply > queueing the jobs on system-wide workqueue? In this case, nothing really, but Péter seems to want to have a dedicated workqueue so that he can later flip HIGHPRI easily if necessary. Usually what a separate workqueue buys are... * It serves as a flushing domain. ie. You can flush work items queued to the same workqueue together. This is useful when individual work items can't be flushed (e.g. they free themselves) or doing so is inefficient. * It serves as an attribute domain. ie. You can set WQ_* flags and @max_active. If using the default values, nothing really is different from using system_wq. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
