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

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

On 5/14/2015 7:50 PM, Hefty, Sean wrote:
> Why can't uverbs simply cleanup all resources associated with the open device, similar to what it does when an app closes unexpectedly (just limited to the device in question)?

When an application closes un-expectedly, the application does not 
attempt to make use of open resources, such as FDs and memory mappings.
In the hot-removal case, the application must *continue* to operate 
without crashing.
For example, the application may want to use other RDMA devices.

In this case, all FDs and memory mappings remain open. The semantics of 
these remaining resources may be device-specific.
The proposed framework first of all allows a provider to indicate 
whether hot-removal is supported (i.e., the presence of the 
'disassociate_ucontext' callback), and if so, allow the provider to 
perform the proper cleanup so that the corresponding user-space driver 
will continue to function.
--
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