dd5bdff83b
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> |
||
---|---|---|
.. | ||
ib_addr.h | ||
ib_cache.h | ||
ib_cm.h | ||
ib_fmr_pool.h | ||
ib_mad.h | ||
ib_marshall.h | ||
ib_pack.h | ||
ib_sa.h | ||
ib_smi.h | ||
ib_umem.h | ||
ib_user_cm.h | ||
ib_user_mad.h | ||
ib_user_sa.h | ||
ib_user_verbs.h | ||
ib_verbs.h | ||
iw_cm.h | ||
Kbuild | ||
rdma_cm.h | ||
rdma_cm_ib.h | ||
rdma_user_cm.h |