Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1433715 > unrolled thread
| Started by | David Vrabel <david.vrabel@citrix.com> |
|---|---|
| First post | 2016-06-29 14:50 +0200 |
| Last post | 2016-06-29 14:50 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [Xen-devel] [PATCH v2] xen: xen-pciback: Remove create_workqueue David Vrabel <david.vrabel@citrix.com> - 2016-06-29 14:50 +0200
| From | David Vrabel <david.vrabel@citrix.com> |
|---|---|
| Date | 2016-06-29 14:50 +0200 |
| Subject | Re: [Xen-devel] [PATCH v2] xen: xen-pciback: Remove create_workqueue |
| Message-ID | <rPn6i-4ei-15@gated-at.bofh.it> |
On 01/06/16 15:15, Bhaktipriya Shridhar wrote: > 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 xen_pcibk_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 thus the increase of local concurrency shouldn't > make any difference. > > Since the work items could be pending, flush_work() has been used in > xen_pcibk_disconnect(). xen_pcibk_xenbus_remove() calls free_pdev() > which in turn calls xen_pcibk_disconnect() for every pdev to ensure that > there is no pending task while disconnecting the driver. Applied to for-linus-4.8, thanks. David
Back to top | Article view | linux.kernel
csiph-web