From: David Vrabel <david.vrabel@citrix.com>
To: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>, <tj@kernel.org>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen: xenbus: Remove create_workqueue
Date: Tue, 31 May 2016 17:18:14 +0100 [thread overview]
Message-ID: <574DB946.1050609@citrix.com> (raw)
In-Reply-To: <20160527185002.GA19321@Karyakshetra>
On 27/05/16 19:50, Bhaktipriya Shridhar wrote:
> With concurrency managed workqueues, use of dedicated workqueues can be
> replaced by using system_wq. Drop xenbus_frontend_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.
>
> Since the work item could be pending and the code expects it to run
> once scheduled, flush_work() has been used in xenbus_dev_suspend()
This says flush_work() but...
>
> Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
> ---
> drivers/xen/xenbus/xenbus_probe.c | 2 ++
> drivers/xen/xenbus/xenbus_probe_frontend.c | 15 +--------------
> 2 files changed, 3 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c
> index 33a31cf..bc97019 100644
> --- a/drivers/xen/xenbus/xenbus_probe.c
> +++ b/drivers/xen/xenbus/xenbus_probe.c
> @@ -592,6 +592,8 @@ int xenbus_dev_suspend(struct device *dev)
>
> DPRINTK("%s", xdev->nodename);
>
> + cancel_work_sync(&xdev->work);
...cancel_work_sync() is called here.
David
next prev parent reply other threads:[~2016-05-31 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 18:50 [PATCH] xen: xenbus: Remove create_workqueue Bhaktipriya Shridhar
2016-05-31 16:18 ` David Vrabel [this message]
2016-05-31 16:43 ` Bhaktipriya Shridhar
2016-05-31 16:43 ` [Xen-devel] " Bhaktipriya Shridhar
2016-05-31 16:18 ` 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=574DB946.1050609@citrix.com \
--to=david.vrabel@citrix.com \
--cc=bhaktipriya96@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.