<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Sean Hefty wrote:
<blockquote cite="mid:000801c8b5e1$27129f20$14c9180a@amr.corp.intel.com"
type="cite">
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
This is my current preferred solution.
</pre>
</blockquote>
I agree.<br>
<blockquote cite="mid:000801c8b5e1$27129f20$14c9180a@amr.corp.intel.com"
type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<br>
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...<br>
<br>
Stevo.<br>
<br>
</body>
</html>