On 12/1/2014 7:50 PM, Sagi Grimberg wrote:
In order to know that we consumed all the connection completions we maintain atomic post_send_buf_count for each IO post send. But we can know that if we post a "beacon" (zero length RECV work request) after we move the QP into error state and the target does not serve any new IO. When we consume it, we know we finished all the connection completion and we can go ahead and destroy stuff.
oops, this patch contains many changes not directly related to the change-log, I guess t either happened by mistake, or we need splitting to 1-2 more patches, e.g removing/delaing with isert_conn->conn_wait_comp_err
-- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
