From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Cc: tj@kernel.org, boris.ostrovsky@oracle.com,
david.vrabel@citrix.com, jgross@suse.com, JBeulich@suse.com,
paul.gortmaker@windriver.com, stefano.stabellini@eu.citrix.com,
cardoe@cardoe.com, xen-devel@lists.xenproject.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen: xen-pciback: Remove create_workqueue
Date: Fri, 27 May 2016 12:01:14 -0400 [thread overview]
Message-ID: <20160527160114.GB1842@char.us.oracle.com> (raw)
In-Reply-To: <20160527155411.GA18039@Karyakshetra>
On Fri, May 27, 2016 at 09:24:11PM +0530, Bhaktipriya Shridhar wrote:
> With concurrency managed workqueues, use of dedicated workqueues can be
> replaced by using system_wq. Drop host->intr_wq by using
> system_wq.
>
> Since there is only a single work item, increase of concurrency level by
> switching to system_wq should not break anything.
_should_ not? Hehe. I presume this has not been tested?
>
> cancel_work_sync() has been used in xen_pcibk_disconnect() to ensure that
> work item is not pending or executing by the time exit path runs.
>
> Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
> ---
> drivers/xen/xen-pciback/pciback.h | 1 -
> drivers/xen/xen-pciback/pciback_ops.c | 2 +-
> drivers/xen/xen-pciback/xenbus.c | 10 +---------
> 3 files changed, 2 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/xen/xen-pciback/pciback.h b/drivers/xen/xen-pciback/pciback.h
> index 4d529f3..7af369b6 100644
> --- a/drivers/xen/xen-pciback/pciback.h
> +++ b/drivers/xen/xen-pciback/pciback.h
> @@ -55,7 +55,6 @@ struct xen_pcibk_dev_data {
>
> /* Used by XenBus and xen_pcibk_ops.c */
> extern wait_queue_head_t xen_pcibk_aer_wait_queue;
> -extern struct workqueue_struct *xen_pcibk_wq;
> /* Used by pcistub.c and conf_space_quirks.c */
> extern struct list_head xen_pcibk_quirks;
>
> diff --git a/drivers/xen/xen-pciback/pciback_ops.c b/drivers/xen/xen-pciback/pciback_ops.c
> index 2f19dd7..f8c7775 100644
> --- a/drivers/xen/xen-pciback/pciback_ops.c
> +++ b/drivers/xen/xen-pciback/pciback_ops.c
> @@ -310,7 +310,7 @@ void xen_pcibk_test_and_schedule_op(struct xen_pcibk_device *pdev)
> * already processing a request */
> if (test_bit(_XEN_PCIF_active, (unsigned long *)&pdev->sh_info->flags)
> && !test_and_set_bit(_PDEVF_op_active, &pdev->flags)) {
> - queue_work(xen_pcibk_wq, &pdev->op_work);
> + schedule_work(&pdev->op_work);
> }
> /*_XEN_PCIB_active should have been cleared by pcifront. And also make
> sure xen_pcibk is waiting for ack by checking _PCIB_op_pending*/
> diff --git a/drivers/xen/xen-pciback/xenbus.c b/drivers/xen/xen-pciback/xenbus.c
> index c252eb3..f70a8e1 100644
> --- a/drivers/xen/xen-pciback/xenbus.c
> +++ b/drivers/xen/xen-pciback/xenbus.c
> @@ -17,7 +17,6 @@
> #include "pciback.h"
>
> #define INVALID_EVTCHN_IRQ (-1)
> -struct workqueue_struct *xen_pcibk_wq;
>
> static bool __read_mostly passthrough;
> module_param(passthrough, bool, S_IRUGO);
> @@ -76,8 +75,7 @@ static void xen_pcibk_disconnect(struct xen_pcibk_device *pdev)
> /* If the driver domain started an op, make sure we complete it
> * before releasing the shared memory */
>
> - /* Note, the workqueue does not use spinlocks at all.*/
> - flush_workqueue(xen_pcibk_wq);
> + cancel_work_sync(&pdev->op_work);
>
> if (pdev->sh_info != NULL) {
> xenbus_unmap_ring_vfree(pdev->xdev, pdev->sh_info);
> @@ -733,11 +731,6 @@ const struct xen_pcibk_backend *__read_mostly xen_pcibk_backend;
>
> int __init xen_pcibk_xenbus_register(void)
> {
> - xen_pcibk_wq = create_workqueue("xen_pciback_workqueue");
> - if (!xen_pcibk_wq) {
> - pr_err("%s: create xen_pciback_workqueue failed\n", __func__);
> - return -EFAULT;
> - }
> xen_pcibk_backend = &xen_pcibk_vpci_backend;
> if (passthrough)
> xen_pcibk_backend = &xen_pcibk_passthrough_backend;
> @@ -747,6 +740,5 @@ int __init xen_pcibk_xenbus_register(void)
>
> void __exit xen_pcibk_xenbus_unregister(void)
> {
> - destroy_workqueue(xen_pcibk_wq);
> xenbus_unregister_driver(&xen_pcibk_driver);
> }
> --
> 2.1.4
>
next prev parent reply other threads:[~2016-05-27 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 15:54 Bhaktipriya Shridhar
2016-05-27 16:01 ` Konrad Rzeszutek Wilk [this message]
2016-05-27 16:08 ` Tejun Heo
2016-05-27 16:32 ` Konrad Rzeszutek Wilk
2016-05-31 10:11 ` David Vrabel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160527160114.GB1842@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=bhaktipriya96@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=cardoe@cardoe.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tj@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®