On Tue, Aug 04, 2015 at 05:03:28PM +0300, Yishai Hadas wrote: > Currently, IB/cma remove_one flow blocks until all user descriptor managed by > IB/ucma are released. This prevents hot-removal of IB devices. This patch > allows IB/cma to remove devices regardless of user space activity. Upon > getting > the RDMA_CM_EVENT_DEVICE_REMOVAL event we close all the underlying HW > resources > for the given ucontext. The ucontext itself is still alive till its explicit > destroying by its creator.
Implementation aside, This changes the policy of the ucma from Tell user space and expect it to synchronously clean up To Tell user space we already nuked the RDMA device asynchronously Do we even want to do that unconditionally? Shouldn't the kernel at least give userspace some time to respond to the event before nuking the world? I'm now also wondering if we have some ordering issues on removal. Will uverbs continue to work while ucma is active? It looks like at least we can rmmod ib_uverbs and stuff goes really sideways for poor apps. That is probably a corner case though.. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
