Re: rdma provider module references

On 12/15/2010 11:09 AM, Roland Dreier wrote: I notice that if I have a user rdma application running that has an rdma connection using iw_cxgb3, then the iw_cxgb3 module reference count is bumped and thus it cannot be unloaded. However when I have an NFSRDMA connection that

Re: rdma provider module references

However I guess NFS/RDMA is behind the RDMA CM, which is supposed to handle device removal. In that code it seems to end up in cma_process_remove(), which appears at first glance to do the right things to destroy all connections etc. Function cma_process_remove() calls cma_remove_id_dev()

rdma provider module references

Hey Roland, I notice that if I have a user rdma application running that has an rdma connection using iw_cxgb3, then the iw_cxgb3 module reference count is bumped and thus it cannot be unloaded. However when I have an NFSRDMA connection that utilizes iw_cxgb3, the module reference count is

Re: rdma provider module references

I notice that if I have a user rdma application running that has an rdma connection using iw_cxgb3, then the iw_cxgb3 module reference count is bumped and thus it cannot be unloaded. However when I have an NFSRDMA connection that utilizes iw_cxgb3, the module reference count is not

Re: rdma provider module references

On 12/15/2010 11:09 AM, Roland Dreier wrote: I notice that if I have a user rdma application running that has an rdma connection using iw_cxgb3, then the iw_cxgb3 module reference count is bumped and thus it cannot be unloaded. However when I have an NFSRDMA connection that