netdev - Re: [net-next v2 1/1] virtual-bus: Implementation of Virtual Bus

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3ef5bc09-dd74-44bc-30f1-b773fac448a2@redhat.com>
Date:   Wed, 20 Nov 2019 13:34:51 +0800
From:   Jason Wang <jasowang@...hat.com>
To:     Jason Gunthorpe <jgg@...pe.ca>
Cc:     "Michael S. Tsirkin" <mst@...hat.com>,
        Parav Pandit <parav@...lanox.com>,
        Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
        davem@...emloft.net, gregkh@...uxfoundation.org,
        Dave Ertman <david.m.ertman@...el.com>, netdev@...r.kernel.org,
        linux-rdma@...r.kernel.org, nhorman@...hat.com,
        sassmann@...hat.com, Kiran Patil <kiran.patil@...el.com>,
        Alex Williamson <alex.williamson@...hat.com>,
        Tiwei Bie <tiwei.bie@...el.com>
Subject: Re: [net-next v2 1/1] virtual-bus: Implementation of Virtual Bus


On 2019/11/20 上午11:59, Jason Wang wrote:
> Well, VFIO have multiple types of API. The design is to stick the VFIO
> DMA model like container work for making DMA API work for userspace
> driver. We can invent something our own but it must duplicate with the
> exist API and it will be extra overhead when VFIO DMA API starts to
> support stuffs like nesting or PASID.
>
> So in conclusion for vhost-mdev:
>
> - DMA is still done through VFIO manner e.g container fd etc.
> - device API is totally virtio specific.
>
> Compared with vfio-pci device, the only difference is the device API,
> we don't use device fd but vhost-net fd,


Correction here, device fd is used here instead of vhost-net fd.

Thanks


>   but of course we can switch
> to use device fd. I'm sure we can settle this part down by having a
> way that is acceptable by both sides.