diff options
| author | Roland Dreier <[email protected]> | 2015-07-23 14:53:32 -0700 |
|---|---|---|
| committer | Nicholas Bellinger <[email protected]> | 2015-08-02 23:11:52 -0700 |
| commit | 109e2381749c1cfd94a0d22b2b54142539024973 (patch) | |
| tree | 9695ecd3738a7bad43edcca4eb641339e7a30060 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 24c7d6c7316c72301bf8ecfc1189fd476176fd75 (diff) | |
target: Drop iSCSI use of mutex around max_cmd_sn increment
In a performance profile, taking a mutex in iscsit_increment_maxcmdsn()
shows up very high. However taking a mutex around "sess->max_cmd_sn += 1"
seems pretty silly: we're not serializing against other contexts in
any useful way.
I did a quick audit and there don't appear to be any other places that
use max_cmd_sn within the mutex more than once, so this lock can't be
providing any useful serialization.
(Get correct values for logging - fix whitespace damage)
Signed-off-by: Roland Dreier <[email protected]>
Signed-off-by: Spencer Baugh <[email protected]>
Signed-off-by: Nicholas Bellinger <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions