netdev - RE: [PATCH iproute2-next v3 0/5] Add vdpa device management tool

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]

Date:   Fri, 5 Feb 2021 17:53:05 +0000
From:   Parav Pandit <parav@...dia.com>
To:     Jason Wang <jasowang@...hat.com>,
        Adrian Moreno <amorenoz@...hat.com>,
        "virtualization@...ts.linux-foundation.org" 
        <virtualization@...ts.linux-foundation.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "dsahern@...il.com" <dsahern@...il.com>,
        "stephen@...workplumber.org" <stephen@...workplumber.org>,
        "mst@...hat.com" <mst@...hat.com>
Subject: RE: [PATCH iproute2-next v3 0/5] Add vdpa device management tool



> From: Jason Wang <jasowang@...hat.com>
> Sent: Friday, February 5, 2021 9:11 AM
> 
> 
> On 2021/2/4 下午7:15, Adrian Moreno wrote:
> > Sorry I have not followed this work as close as I would have wanted.
> > Some questions below.
> >
> > On 2/4/21 4:16 AM, Jason Wang wrote:
> >> On 2021/2/2 下午6:35, Parav Pandit wrote:
> >>> Linux vdpa interface allows vdpa device management functionality.
> >>> This includes adding, removing, querying vdpa devices.
> >>>
> >>> vdpa interface also includes showing supported management devices
> >>> which support such operations.
> >>>
> >>> This patchset includes kernel uapi headers and a vdpa tool.
> >>>
> >>> examples:
> >>>
> >>> $ vdpa mgmtdev show
> >>> vdpasim:
> >>>     supported_classes net
> >>>
> >>> $ vdpa mgmtdev show -jp
> >>> {
> >>>       "show": {
> >>>           "vdpasim": {
> >>>               "supported_classes": [ "net" ]
> >>>           }
> >>>       }
> >>> }
> >>>
> > How can a user establish the relationship between a mgmtdev and it's
> > parent device (pci vf, sf, etc)?
> 
> 
> Parav should know more but I try to answer.
> 
> I think there should be BDF information in the mgmtdev show command if
> the parent is a PCI device, or we can simply show the parent here?
>
Yes, it is present in the mgmtdev show command.
I should have added the example from the kernel cover letter here.
Link to the kernel cover letter is at 

An example for real PCI PF,VF,SF device looks like below.
I will cover below example to the v4 cover letter while addressing David's comment for header file relocation.

$ vdpa mgmtdev list
pci/0000:03.00:0
  supported_classes
    net
pci/0000:03.00:4
  supported_classes
    net
auxiliary/mlx5_core.sf.8
  supported_classes
    net

[1] https://lore.kernel.org/netdev/20210105103203.82508-1-parav@nvidia.com/