From: Mike Christie <michael.christie@oracle.com>
To: stefanha@redhat.com, jasowang@redhat.com, mst@redhat.com,
sgarzare@redhat.com, virtualization@lists.linux-foundation.org,
arbn@yandex-team.com
Subject: [PATCH V3 0/8] vhost flush cleanups
Date: Tue, 17 May 2022 13:08:42 -0500 [thread overview]
Message-ID: <20220517180850.198915-1-michael.christie@oracle.com> (raw)
The following patches made over linus's/mst's tree 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.
V3:
- Fix test.c flush use.
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 reply other threads:[~2022-05-17 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 18:08 Mike Christie [this message]
2022-05-17 18:08 ` [PATCH V3 1/8] vhost: get rid of vhost_poll_flush() wrapper Mike Christie
2022-05-17 18:08 ` [PATCH V3 2/8] vhost: flush dev once during vhost_dev_stop Mike Christie
2022-05-17 18:08 ` [PATCH V3 3/8] vhost_net: get rid of vhost_net_flush_vq() and extra flush calls Mike Christie
2022-05-17 18:08 ` [PATCH V3 4/8] vhost_test: remove vhost_test_flush_vq() Mike Christie
2022-05-18 7:27 ` Stefano Garzarella
2022-05-17 18:08 ` [PATCH V3 5/8] vhost_vsock: simplify vhost_vsock_flush() Mike Christie
2022-05-17 18:08 ` [PATCH V3 6/8] vhost-scsi: drop flush after vhost_dev_cleanup Mike Christie
2022-05-17 18:08 ` [PATCH V3 7/8] vhost-test: " Mike Christie
2022-05-17 18:08 ` [PATCH V3 8/8] vhost: rename vhost_work_dev_flush Mike Christie
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=20220517180850.198915-1-michael.christie@oracle.com \
--to=michael.christie@oracle.com \
--cc=arbn@yandex-team.com \
--cc=jasowang@redhat.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).