On Wed, Feb 5, 2025 at 8:17 PM Jason Gunthorpe <jgg@xxxxxxxx> wrote: > > On Wed, Feb 05, 2025 at 01:54:14PM +0530, Kalesh Anakkur Purayil wrote: > > > Shouldn't devlink reload completely release all auxiliary drivers? > > > Why are you keeping BNXT RDMA driver during reload? > > > > That is the current design. BNXT core Ethernet driver will not destroy > > the auxiliary device for RDMA, but just calls the suspend callback. As > > a result, RDMA driver will remains loaded and remains registered with > > the Ethernet driver instance. > > What is the difference between your suspend and reloading the driver?? > > Do you keep the ib device registered during suspend and all uverbs > contexts open? How does that work??? We unregister the IB device in both cases. The only difference is in the suspend path, the communication channel with the Ethernet driver is still active. As a result, the ethernet driver may invoke ULP callbacks even though the IB device is removed. As I mentioned in my last response to Leon, we are working on to improve this design to remove the auxiliary device completely instead of invoking auxdrv->suspend. > > Jason -- Regards, Kalesh AP
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
