diff options
author | Sagi Grimberg <[email protected]> | 2014-05-19 17:44:23 +0300 |
---|---|---|
committer | Nicholas Bellinger <[email protected]> | 2014-05-19 14:38:49 -0700 |
commit | 9d49f5e284e700576f3b65f1e28dea8539da6661 (patch) | |
tree | b780028276b9f5261b23505d3c16197a4964a2d4 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | e346ab343f4f58c12a96725c7b13df9cc2ad56f6 (diff) |
Target/iser: Fix hangs in connection teardown
In ungraceful teardowns isert close flows seem racy such that
isert_wait_conn hangs as RDMA_CM_EVENT_DISCONNECTED never
gets invoked (no one called rdma_disconnect).
Both graceful and ungraceful teardowns will have rx flush errors
(isert posts a batch once connection is established). Once all
flush errors are consumed we invoke isert_wait_conn and it will
be responsible for calling rdma_disconnect. This way it can be
sure that rdma_disconnect was called and it won't wait forever.
This patch also removes the logout_posted indicator. either the
logout completion was consumed and no problem decrementing the
post_send_buf_count, or it was consumed as a flush error. no point
of keeping it for isert_wait_conn as there is no danger that
isert_conn will be accidentally removed while it is running.
(Drop unnecessary sleep_on_conn_wait_comp check in
isert_cq_rx_comp_err - nab)
Signed-off-by: Sagi Grimberg <[email protected]>
Cc: [email protected] # 3.10+
Signed-off-by: Nicholas Bellinger <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions