From: Stefano Garzarella <sgarzare@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Gautam Dawar <gautam.dawar@xilinx.com>,
eperezma@redhat.com
Cc: jasowang@redhat.com, qemu-devel@nongnu.org, gdawar@xilinx.com,
martinh@xilinx.com, hanand@xilinx.com, tanujk@xilinx.com,
pabloc@xilinx.com
Subject: Re: [PATCH 2/2] Allow VIRTIO_F_IN_ORDER to be negotiated for vdpa devices
Date: Thu, 17 Feb 2022 15:29:10 +0100 [thread overview]
Message-ID: <20220217142910.eovyddvvpxkvzchf@sgarzare-redhat> (raw)
In-Reply-To: <20220217023150-mutt-send-email-mst@kernel.org>
On Thu, Feb 17, 2022 at 02:32:48AM -0500, Michael S. Tsirkin wrote:
>On Tue, Feb 15, 2022 at 12:52:31PM +0530, Gautam Dawar wrote:
>> This patch adds the ability to negotiate VIRTIO_F_IN_ORDER bit
>> for vhost-vdpa backend when the underlying device supports this
>> feature.
>> This would aid in reaping performance benefits with HW devices
>> that implement this feature. At the same time, it shouldn't have
>> any negative impact as vhost-vdpa backend doesn't involve any
>> userspace virtqueue operations.
>>
>> Signed-off-by: Gautam Dawar <gdawar@xilinx.com>
>
>Having features that hardware implements but qemu does not
>means we can't migrate between them.
>So I'd rather see a userspace implementation.
FYI Jason proposed to support VIRTIO_F_IN_ORDER in QEMU/Linux as an idea
for the next GSoC/Outreachy. I offered to mentor and prepared a project
description [1], if anyone else is interested, it would be great to have
a co-mentor :-)
Thanks,
Stefano
[1] https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg04032.html
next prev parent reply other threads:[~2022-02-17 15:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 7:22 [PATCH 0/2] Allow VIRTIO_F_IN_ORDER negotiation with vhost-vdpa Gautam Dawar
2022-02-15 7:22 ` [PATCH 1/2] linux headers: update against Linux 5.17-rc4 Gautam Dawar
2022-02-17 7:17 ` Jason Wang
2022-02-17 9:06 ` Gautam Dawar
2022-02-15 7:22 ` [PATCH 2/2] Allow VIRTIO_F_IN_ORDER to be negotiated for vdpa devices Gautam Dawar
2022-02-15 15:22 ` Eugenio Perez Martin
2022-02-17 7:16 ` Jason Wang
2022-02-17 8:27 ` Gautam Dawar
2022-02-17 8:32 ` Michael S. Tsirkin
2022-02-17 8:54 ` Eugenio Perez Martin
2022-02-17 7:32 ` Michael S. Tsirkin
2022-02-17 14:29 ` Stefano Garzarella [this message]
2022-02-18 10:24 ` Eugenio Perez Martin
2022-02-18 16:57 ` Stefano Garzarella
2022-02-18 10:22 ` Eugenio Perez Martin
2022-02-21 4:31 ` Jason Wang
2022-02-18 11:09 ` Michael S. Tsirkin
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=20220217142910.eovyddvvpxkvzchf@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=eperezma@redhat.com \
--cc=gautam.dawar@xilinx.com \
--cc=gdawar@xilinx.com \
--cc=hanand@xilinx.com \
--cc=jasowang@redhat.com \
--cc=martinh@xilinx.com \
--cc=mst@redhat.com \
--cc=pabloc@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=tanujk@xilinx.com \
/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).