From: Jason Wang <jasowang@redhat.com>
To: Mike Christie <michael.christie@oracle.com>,
stefanha@redhat.com, mst@redhat.com, sgarzare@redhat.com,
virtualization@lists.linux-foundation.org, arbn@yandex-team.com
Subject: Re: [PATCH V2 2/8] vhost: flush dev once during vhost_dev_stop
Date: Tue, 17 May 2022 11:16:22 +0800 [thread overview]
Message-ID: <3d4600f1-b34d-ffad-256b-65cba1c9c380@redhat.com> (raw)
In-Reply-To: <20220515202922.174066-3-michael.christie@oracle.com>
在 2022/5/16 04:29, Mike Christie 写道:
> When vhost_work_dev_flush returns all work queued at that time will have
> completed. There is then no need to flush after every vhost_poll_stop
> call, and we can move the flush call to after the loop that stops the
> pollers.
>
> Signed-off-by: Mike Christie <michael.christie@oracle.com>
Acked-by: Jason Wang <jasowang@redhat.com>
> ---
> drivers/vhost/vhost.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
> index 1d84a2818c6f..9f8de04bb673 100644
> --- a/drivers/vhost/vhost.c
> +++ b/drivers/vhost/vhost.c
> @@ -653,11 +653,11 @@ void vhost_dev_stop(struct vhost_dev *dev)
> int i;
>
> for (i = 0; i < dev->nvqs; ++i) {
> - if (dev->vqs[i]->kick && dev->vqs[i]->handle_kick) {
> + if (dev->vqs[i]->kick && dev->vqs[i]->handle_kick)
> vhost_poll_stop(&dev->vqs[i]->poll);
> - vhost_work_dev_flush(dev->vqs[i]->poll.dev);
> - }
> }
> +
> + vhost_work_dev_flush(dev);
> }
> EXPORT_SYMBOL_GPL(vhost_dev_stop);
>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-05-17 3:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 20:29 [PATCH V2 0/8] vhost flush cleanups Mike Christie
2022-05-15 20:29 ` [PATCH V2 1/8] vhost: get rid of vhost_poll_flush() wrapper Mike Christie
2022-05-17 3:14 ` Jason Wang
2022-05-17 13:56 ` Stefano Garzarella
2022-05-15 20:29 ` [PATCH V2 2/8] vhost: flush dev once during vhost_dev_stop Mike Christie
2022-05-17 3:16 ` Jason Wang [this message]
2022-05-17 13:57 ` Stefano Garzarella
2022-05-15 20:29 ` [PATCH V2 3/8] vhost_net: get rid of vhost_net_flush_vq() and extra flush calls Mike Christie
2022-05-17 3:22 ` Jason Wang
2022-05-17 14:06 ` Stefano Garzarella
2022-05-15 20:29 ` [PATCH V2 4/8] vhost_test: remove vhost_test_flush_vq() Mike Christie
2022-05-17 3:23 ` Jason Wang
2022-05-17 14:11 ` Stefano Garzarella
2022-05-17 16:54 ` Mike Christie
2022-05-15 20:29 ` [PATCH V2 5/8] vhost_vsock: simplify vhost_vsock_flush() Mike Christie
2022-05-17 3:23 ` Jason Wang
2022-05-15 20:29 ` [PATCH V2 6/8] vhost-scsi: drop flush after vhost_dev_cleanup Mike Christie
2022-05-15 20:29 ` [PATCH V2 7/8] vhost-test: " Mike Christie
2022-05-17 3:28 ` Jason Wang
2022-05-15 20:29 ` [PATCH V2 8/8] vhost: rename vhost_work_dev_flush Mike Christie
2022-05-17 3:28 ` Jason Wang
2022-05-17 14:18 ` Stefano Garzarella
2022-05-17 3:13 ` [PATCH V2 0/8] vhost flush cleanups Jason Wang
2022-05-17 14:20 ` Stefano Garzarella
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=3d4600f1-b34d-ffad-256b-65cba1c9c380@redhat.com \
--to=jasowang@redhat.com \
--cc=arbn@yandex-team.com \
--cc=michael.christie@oracle.com \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).