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  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:   Thu, 7 May 2020 14:04:04 +0000
From:   "Saleem, Shiraz" <>
To:     Greg KH <>,
        "Kirsher, Jeffrey T" <>
CC:     "" <>,
        "Ertman, David M" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "Nguyen, Anthony L" <>,
        "Bowers, AndrewX" <>
Subject: RE: [net-next v3 2/9] ice: Create and register virtual bus for RDMA

> Subject: Re: [net-next v3 2/9] ice: Create and register virtual bus for RDMA
> On Wed, May 06, 2020 at 02:04:58PM -0700, Jeff Kirsher wrote:
> > From: Dave Ertman <>
> >
> > The RDMA block does not have its own PCI function, instead it must
> > utilize the ice driver to gain access to the PCI device. Create a
> > virtual bus device so the irdma driver can register a virtual bus
> > driver to bind to it and receive device data. The device data contains
> > all of the relevant information that the irdma peer will need to
> > access this PF's IIDC API callbacks.
> But there is no virtual bus driver in this patch!

Hi Greg - 

The irdma driver is the virtbus driver that would bind to the virtual devices created
in this netdev driver.

It is decoupled from this series as it was deemed in a prior discussion that irdma driver
would go in a +1 cycle from net series to avoid conflicts. See discussion here --

The irdma driver is currently posted as an RFC series with its most recent submission here --


Powered by blists - more mailing lists