Re: [RESEND PATCH V3 for-next 0/3] HW Device hot-removal support

[Yishai Hadas <yishaih-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>]

On 5/13/2015 11:55 PM, Hefty, Sean wrote:
> Please look at ib_user_mad and how it handles device removal with active clients.  We should be able to follow the same model that doesn't require driving changes down into every driver.
>

The ib_uverbs code does follow the same model in the sense that the 
context (uverbs_device) associated with the fd remains open until the 
app closes it, while all references to the HW device are removed 
immediately. However, in contrast to the umad API, which does *not* 
expose direct HW access and thus can be managed in a device-independent 
manner, ib_uverbs does provide user-space direct HW access.
Therefore, detaching a ib_uverbs context from a HW device does require 
device-specific logic.
The amount of code depends on the specific driver. The proposed 
framework provides any driver a chance to do proper cleanup when devices 
are removed.



--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html