diff options
author | 2014-05-19 17:44:24 +0300 | |
---|---|---|
committer | 2014-05-20 11:17:40 -0700 | |
commit | 88c4015fda6d014392f76d3b1688347950d7a12d (patch) | |
tree | 344353885fd0c7781c6483cd245724d88fa3a8f7 /tools/perf/scripts/python/syscall-counts.py | |
parent | Target/iser: Fix hangs in connection teardown (diff) | |
download | linux-dev-88c4015fda6d014392f76d3b1688347950d7a12d.tar.xz linux-dev-88c4015fda6d014392f76d3b1688347950d7a12d.zip |
Target/iser: Improve cm events handling
There are 4 RDMA_CM events that all basically mean that
the user should teardown the IB connection:
- DISCONNECTED
- ADDR_CHANGE
- DEVICE_REMOVAL
- TIMEWAIT_EXIT
Only in DISCONNECTED/ADDR_CHANGE it makes sense to
call rdma_disconnect (send DREQ/DREP to our initiator).
So we keep the same teardown handler for all of them
but only indicate calling rdma_disconnect for the relevant
events.
This patch also removes redundant debug prints for each single
event.
v2 changes:
- Call isert_disconnected_handler() for DEVICE_REMOVAL (Or + Sag)
Signed-off-by: Sagi Grimberg <sagig@mellanox.com>
Cc: stable@vger.kernel.org # 3.10+
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions