diff options
author | Bhaktipriya Shridhar <bhaktipriya96@gmail.com> | 2016-05-31 22:26:30 +0530 |
---|---|---|
committer | David Vrabel <david.vrabel@citrix.com> | 2016-07-06 10:34:49 +0100 |
commit | 5ee405d9d234ee5641741c07a654e4c6ba3e2a9d (patch) | |
tree | 8c923aa6dcd382694839a72fcfa0245510804e5e /arch | |
parent | 429eafe60943bdfa33b15540ab2db5642a1f8c3c (diff) | |
download | linux-stable-5ee405d9d234ee5641741c07a654e4c6ba3e2a9d.tar.gz linux-stable-5ee405d9d234ee5641741c07a654e4c6ba3e2a9d.tar.bz2 linux-stable-5ee405d9d234ee5641741c07a654e4c6ba3e2a9d.zip |
xen: xenbus: Remove create_workqueue
System workqueues have been able to handle high level of concurrency
for a long time now and there's no reason to use dedicated workqueues
just to gain concurrency. Replace dedicated xenbus_frontend_wq with the
use of system_wq.
Unlike a dedicated per-cpu workqueue created with create_workqueue(),
system_wq allows multiple work items to overlap executions even on
the same CPU; however, a per-cpu workqueue doesn't have any CPU
locality or global ordering guarantees unless the target CPU is
explicitly specified and the increase of local concurrency shouldn't
make any difference.
In this case, there is only a single work item, increase of concurrency
level by switching to system_wq should not make any difference.
Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Acked-by: Tejun Heo <tj@kernel.org>
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions