From: "Michael S. Tsirkin" <mst@redhat.com>
To: Srujana Challa <schalla@marvell.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Vamsi Krishna Attunuru <vattunuru@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: Regarding VIRTIO_F_IN_ORDER and VIRTIO_F_NOTIFICATION_DATA feature bits
Date: Wed, 13 Dec 2023 11:45:10 -0500 [thread overview]
Message-ID: <20231213114214-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <BYAPR18MB2791DF7E6C0F61E2D8698E8FA08DA@BYAPR18MB2791.namprd18.prod.outlook.com>
On Wed, Dec 13, 2023 at 04:27:40PM +0000, Srujana Challa wrote:
> Hi Michael,
>
> While verifying virtio frontend drivers of guest OS on qemu with vhost-vdpa backend,
> we came across feature bits VIRTIO_F_IN_ORDER and VIRTIO_F_NOTIFICATION_DATA,
> which are introduced in virtio 1.1 spec, are not yet enabled in qemu. These feature flags
> are very much useful for achieving better virtio-net performance and most of the latest
> hardware VDPA devices supports these feature flags as per of virtio spec.
Could you share more about which device do you mean? Does Marvell ship
or intends to ship one?
> Could you let us know if there are any plans, to add support for these features in upcoming
> qemu releases.
> I guess there was some discussion on VIRTIO_F_IN_ORDER feature bit long ago,
> https://patchew.org/QEMU/1533833677-27512-1-git-send-email-i.maximets@samsung.com/
> Seems like that discussion has not reached any conclusion or further work.
>
> Thanks,
> Srujana.
Yes that patch got comments and these were not addressed.
Feel free to address them so this can proceed.
--
MST
next prev parent reply other threads:[~2023-12-13 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 16:27 Regarding VIRTIO_F_IN_ORDER and VIRTIO_F_NOTIFICATION_DATA feature bits Srujana Challa
2023-12-13 16:45 ` Michael S. Tsirkin [this message]
2023-12-14 6:08 ` [EXT] " Srujana Challa
2023-12-14 8:05 ` Srujana Challa
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=20231213114214-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jerinj@marvell.com \
--cc=qemu-devel@nongnu.org \
--cc=schalla@marvell.com \
--cc=vattunuru@marvell.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 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.