netdev - Re: [RFC 2/2] be2net: Added functionality to support RoCE driver

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: <CAL1RGDWB3jgBMZAiE6guNgFy-QVvh4NBj1sXd6k7eK1hDnv51Q@mail.gmail.com>
Date:	Thu, 8 Mar 2012 10:08:19 -0800
From:	Roland Dreier <roland@...estorage.com>
To:	Francois Romieu <romieu@...zoreil.com>
Cc:	parav.pandit@...lex.com, netdev@...r.kernel.org,
	linux-rdma@...r.kernel.org
Subject: Re: [RFC 2/2] be2net: Added functionality to support RoCE driver

On Thu, Mar 8, 2012 at 3:48 AM, Francois Romieu <romieu@...zoreil.com> wrote:
> Are there real use-cases where the device and the ocrdma_drv could be
> loaded in different relative ordering ?

Yes -- two cases are pretty standard:

 - be2net driver loads, probes all devices, then roce driver loads
 - be2net and roce driver loads, then a device is probed later
   (PCI hotplug, new SR-IOV virtual function, etc)

so we need to deal with the case where both the core be2net driver
is probing devices and the roce driver loads later, and also the case
where the roce driver loads first and then gets notified as the be2net
driver probes a device.

(This is pretty much the same as mlx4_core / mlx4_ib BTW)

 - R.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html