aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorNicholas Bellinger <[email protected]>2016-10-30 18:58:39 -0700
committerNicholas Bellinger <[email protected]>2017-03-30 20:35:07 -0700
commit555a65f66c3c4d9dd46a565418b0b655d861a723 (patch)
tree222a3f42db2688223849108bf7fe4b5a1b2f07d4 /tools/perf/scripts/python/call-graph-from-postgresql.py
parenta4467018c2a7228f4ef58051f0511bd037bff264 (diff)
iser-target: Fix queue-full response handling
This patch addresses two queue-full handling bugs in iser-target. The first is propagating isert_rdma_rw_ctx_post() return back to target-core via isert_put_datain() + isert_get_dataout() callbacks, in order to trigger queue-full logic in target-core. Note target-core expects -EAGAIN or -ENOMEM error to signal RDMA WRITE/READ data-transfer callbacks should be retried, after queue-full logic been invoked. Other types of errors propagated up from RDMA RW API will result in target-core generating internal CHECK_CONDITION status, avoiding subsequent isert_put_datain() and isert_get_dataout() iscsit_transport callback retry attempts. The second is to use transport_generic_request_failure() during T10-PI hw-offload errors in isert_rdma_write_done() and isert_rdma_read_done(), so CHECK_CONDITION queue-full is handled internally by target-core. Also add isert_put_response() T10-PI failure case fixme in isert_rdma_write_done(), which is currently not internally retried or released until session reinstatement. Reported-by: Potnuri Bharat Teja <[email protected]> Reviewed-by: Potnuri Bharat Teja <[email protected]> Tested-by: Potnuri Bharat Teja <[email protected]> Cc: Potnuri Bharat Teja <[email protected]> Reported-by: Steve Wise <[email protected]> Cc: Steve Wise <[email protected]> Cc: Sagi Grimberg <[email protected]> Signed-off-by: Nicholas Bellinger <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions