aboutsummaryrefslogtreecommitdiffstats
path: root/include/rdma
diff options
context:
space:
mode:
authorOr Gerlitz <ogerlitz@voltaire.com>2008-07-22 14:14:22 -0700
committerRoland Dreier <rolandd@cisco.com>2008-07-22 14:14:22 -0700
commitdd5bdff83b19d9174126e0398b47117c3a80e22d (patch)
tree2bdbc102afcc851d1cd0bef07e3a47d4e9ec1ae9 /include/rdma
parentd35cb360c29956510b2fe1a953bd4968536f7216 (diff)
downloadmrst-s0i3-test-dd5bdff83b19d9174126e0398b47117c3a80e22d.tar.gz
mrst-s0i3-test-dd5bdff83b19d9174126e0398b47117c3a80e22d.tar.xz
mrst-s0i3-test-dd5bdff83b19d9174126e0398b47117c3a80e22d.zip
RDMA/cma: Add RDMA_CM_EVENT_ADDR_CHANGE event
Add an RDMA_CM_EVENT_ADDR_CHANGE event can be used by rdma-cm consumers that wish to have their RDMA sessions always use the same links (eg <hca/port>) as the IP stack does. In the current code, this does not happen when bonding is used and fail-over happened but the IB link used by an already existing session is operating fine. Use the netevent notification for sensing that a change has happened in the IP stack, then scan the rdma-cm ID list to see if there is an ID that is "misaligned" with respect to the IP stack, and deliver RDMA_CM_EVENT_ADDR_CHANGE for this ID. The consumer can act on the event or just ignore it. Signed-off-by: Or Gerlitz <ogerlitz@voltaire.com> Signed-off-by: Roland Dreier <rolandd@cisco.com>
Diffstat (limited to 'include/rdma')
-rw-r--r--include/rdma/rdma_cm.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/include/rdma/rdma_cm.h b/include/rdma/rdma_cm.h
index 22bb2e7bab1..001d606517f 100644
--- a/include/rdma/rdma_cm.h
+++ b/include/rdma/rdma_cm.h
@@ -57,7 +57,8 @@ enum rdma_cm_event_type {
RDMA_CM_EVENT_DISCONNECTED,
RDMA_CM_EVENT_DEVICE_REMOVAL,
RDMA_CM_EVENT_MULTICAST_JOIN,
- RDMA_CM_EVENT_MULTICAST_ERROR
+ RDMA_CM_EVENT_MULTICAST_ERROR,
+ RDMA_CM_EVENT_ADDR_CHANGE
};
enum rdma_port_space {