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 0/8] vhost flush cleanups
Date: Tue, 17 May 2022 11:13:39 +0800 [thread overview]
Message-ID: <2401fa32-bcbe-614a-9305-9b91e97f7d7f@redhat.com> (raw)
In-Reply-To: <20220515202922.174066-1-michael.christie@oracle.com>
在 2022/5/16 04:29, Mike Christie 写道:
> The following patches are Andrey Ryabinin's flush cleanups and some
> from me. They reduce the number of flush calls and remove some bogus
> ones where we don't even have a worker running anymore or they were
> based on outdated or incorrect assumptions.
>
> Jason, for the patches you gave me an explicit acked/reviewed tag I
> added it. For the replies where I answered your review questions and
> you only replied with an affirimative reply I did not add a tag,
> because I was not not 100% sure what you wanted to do.
Fine, I will go through the codes.
Thanks
>
> These patches will be used in the vhost threading patches which I think
> will make progress again now that I have Christian's email figured out
> :) (he had moved to microsoft but I've been using the ubuntu address).
> I think the patches are ok cleanups in general so I thought they could
> get merged separately if people agree.
>
> V2:
> - Added patch to rename vhost_work_dev_flush to just vhost_dev_flush
> to handle review comment from Jason about the naming not being so
> great.
>
>
_______________________________________________
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:13 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
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 ` Jason Wang [this message]
2022-05-17 14:20 ` [PATCH V2 0/8] vhost flush cleanups 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=2401fa32-bcbe-614a-9305-9b91e97f7d7f@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).