[openib-general] Re: RDMA Generic Connection Management

[Steve Wise]

Tom,

Can explain this in more detail?  I don't see how this is any different
from the current openib client registration design?  If I understand the
openib implementation correctly, a ULP registers as an ib client,  and
gets notified of all new devices aswell as all device removals via
upcalls.  The ULP _must_ clean up all allocated device resources in its
remove function (and even sleep need be?).  

How is that different from a dapl consumer having to process an async
EVD about device removal, and shut down all EPs and EVDs that use that
device?

I'm not advocating necessarily that the client add/remove is the way to
go vs shielding ULPs from this totally, but I want to understand how
EVDs help things.

Thanks,

Steve.

 

> -----Original Message-----
> From: Talpey, Thomas [mailto:Thomas.Talpey at netapp.com] 
> Sent: Tuesday, August 30, 2005 3:11 PM
> To: Roland Dreier
> Cc: Steve Wise; openib-general at openib.org
> Subject: Re: [openib-general] Re: RDMA Generic Connection Management
> 
> At 03:08 PM 8/30/2005, Roland Dreier wrote:
> >    Thomas> kDAPL does this!  :-)
> >
> >Does what?  As far as I can tell kDAPL just ignores hotplug and
> >routing and hopes the problems go away ;)
> 
> I was referring to kDAPL's architecture, which does in fact address
> hotplug with async evd upcalls. In the early days of the reference
> port we implemented it on Solaris this way, for example.
> 
> Tom.
>