[alsa-devel] [PATCH v4 11/18] input: Add initial support for TWL6040 vibrator

Tejun Heo tj at kernel.org
Sat Jun 18 17:36:38 CEST 2011


2011/6/18 Dmitry Torokhov <dmitry.torokhov at gmail.com>:
> 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

* 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.



More information about the Alsa-devel mailing list