diff options
| author | Tejun Heo <tj@kernel.org> | 2010-07-02 10:03:51 +0200 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2010-07-02 11:00:08 +0200 |
| commit | c7fc77f78f16d138ca997ce096a62f46e2e9420a (patch) | |
| tree | 0478e5dde66f6ff86d4baa0fe541748e1a6f1ed2 /kernel/async.c | |
| parent | f34217977d717385a3e9fd7018ac39fade3964c0 (diff) | |
| download | linux-c7fc77f78f16d138ca997ce096a62f46e2e9420a.tar.gz linux-c7fc77f78f16d138ca997ce096a62f46e2e9420a.tar.bz2 linux-c7fc77f78f16d138ca997ce096a62f46e2e9420a.zip | |
workqueue: remove WQ_SINGLE_CPU and use WQ_UNBOUND instead
WQ_SINGLE_CPU combined with @max_active of 1 is used to achieve full
ordering among works queued to a workqueue. The same can be achieved
using WQ_UNBOUND as unbound workqueues always use the gcwq for
WORK_CPU_UNBOUND. As @max_active is always one and benefits from cpu
locality isn't accessible anyway, serving them with unbound workqueues
should be fine.
Drop WQ_SINGLE_CPU support and use WQ_UNBOUND instead. Note that most
single thread workqueue users will be converted to use multithread or
non-reentrant instead and only the ones which require strict ordering
will keep using WQ_UNBOUND + @max_active of 1.
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'kernel/async.c')
0 files changed, 0 insertions, 0 deletions