[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/2] Allow VIRTIO_F_IN_ORDER to be negotiated for vdpa device
From: |
Eugenio Perez Martin |
Subject: |
Re: [PATCH 2/2] Allow VIRTIO_F_IN_ORDER to be negotiated for vdpa devices |
Date: |
Fri, 18 Feb 2022 11:24:23 +0100 |
On Thu, Feb 17, 2022 at 3:29 PM Stefano Garzarella <sgarzare@redhat.com> wrote:
>
> 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 :-)
>
I'd be happy to co-mentor for sure, should I edit the wiki to reflect it?
Thanks!
> Thanks,
> Stefano
>
> [1] https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg04032.html
>
Re: [PATCH 2/2] Allow VIRTIO_F_IN_ORDER to be negotiated for vdpa devices, Michael S. Tsirkin, 2022/02/18