Steve Wise wrote:
Sean Hefty wrote:
1) Merely enable the application to know when there has been
a significant change in IP routing. If the current services are
inadequate for this purpose then extend those rather than
do an automatic connection teardown/rebuild.
This is my current preferred solution.
I agree.
I don't have an issue with the rdma_cm issuing some sort of notification event
when an IP address mapping changes. I would use an event name that indicated
this, rather than 'disconnect'.
If this is implemented, I'd like to minimize the overhead per rdma_cm_id
required to report this event.
Maybe instead of making this a cm_id event, we should add a concept of
rdma async events that aren't necessarily affiliated with any
particular cm_id? IE a new channel for these types. Then you can
post it once when a route changes that affects rdma devices, for
example...
As opposed to posting the event to every cm_id affected...
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
