On 10/13/2015 11:52 PM, Sagi Grimberg wrote:
Another question, I notice that you wake_up cmd_list_wq even if the
session is not tearing down (where transport_free_session is not
running). Won't that introduce extra work in the hot path of command
processing?
Hello Sagi,
This should be fine since the wake_up() function is only called from
target_release_cmd_kref() after the command list became empty. That
means after a response has been sent and while no other commands are
being processed for the same session.
Bart.
--
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
