On Fri, Sep 22, 2023 at 11:39:19AM -0400, Michael S. Tsirkin wrote: > On Fri, Sep 22, 2023 at 09:25:01AM -0300, Jason Gunthorpe wrote: > > On Fri, Sep 22, 2023 at 11:02:50AM +0800, Jason Wang wrote: > > > On Fri, Sep 22, 2023 at 3:53 AM Jason Gunthorpe <jgg@xxxxxxxxxx> wrote: > > > > > > > > On Thu, Sep 21, 2023 at 03:34:03PM -0400, Michael S. Tsirkin wrote: > > > > > > > > > that's easy/practical. If instead VDPA gives the same speed with just > > > > > shadow vq then keeping this hack in vfio seems like less of a problem. > > > > > Finally if VDPA is faster then maybe you will reconsider using it ;) > > > > > > > > It is not all about the speed. > > > > > > > > VDPA presents another large and complex software stack in the > > > > hypervisor that can be eliminated by simply using VFIO. > > > > > > vDPA supports standard virtio devices so how did you define > > > complexity? > > > > As I said, VFIO is already required for other devices in these VMs. So > > anything incremental over base-line vfio-pci is complexity to > > minimize. > > > > Everything vdpa does is either redundant or unnecessary compared to > > VFIO in these environments. > > > > Jason > > Yes but you know. There are all kind of environments. I guess you > consider yours the most mainstream and important, and are sure it will > always stay like this. But if there's a driver that does what you need > then you use that. Come on, you are the one saying we cannot do things in the best way possible because you want your way of doing things to be the only way allowed. Which of us thinks "yours the most mainstream and important" ?? I'm not telling you to throw away VPDA, I'm saying there are legimitate real world use cases where VFIO is the appropriate interface, not VDPA. I want choice, not dogmatic exclusion that there is Only One True Way. > You really should be explaining what vdpa *does not* do that you > need. I think I've done that enough, but if you have been following my explanation you should see that the entire point of this design is to allow a virtio device to be created inside a DPU to a specific detailed specification (eg an AWS virtio-net device, for instance) The implementation is in the DPU, and only the DPU. At the end of the day VDPA uses mediation and creates some RedHat/VDPA/Qemu virtio-net device in the guest. It is emphatically NOT a perfect recreation of the "AWS virtio-net" we started out with. It entirely fails to achieve the most important thing it needs to do! Yishai will rework the series with your remarks, we can look again on v2, thanks for all the input! Jason
