diff options
| author | Or Gerlitz <ogerlitz@voltaire.com> | 2008-07-22 14:14:22 -0700 |
|---|---|---|
| committer | Roland Dreier <rolandd@cisco.com> | 2008-07-22 14:14:22 -0700 |
| commit | dd5bdff83b19d9174126e0398b47117c3a80e22d (patch) | |
| tree | 2bdbc102afcc851d1cd0bef07e3a47d4e9ec1ae9 /net | |
| parent | d35cb360c29956510b2fe1a953bd4968536f7216 (diff) | |
| download | linux-3.10-dd5bdff83b19d9174126e0398b47117c3a80e22d.tar.gz linux-3.10-dd5bdff83b19d9174126e0398b47117c3a80e22d.tar.bz2 linux-3.10-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 'net')
0 files changed, 0 insertions, 0 deletions