diff options
| author | Roland Dreier | 2015-07-23 23:53:32 +0200 |
|---|---|---|
| committer | Nicholas Bellinger | 2015-08-03 08:11:52 +0200 |
| commit | 109e2381749c1cfd94a0d22b2b54142539024973 (patch) | |
| tree | 9695ecd3738a7bad43edcca4eb641339e7a30060 /drivers/target/iscsi/iscsi_target_tpg.c | |
| parent | qla2xxx: Update tcm_qla2xxx module description to 24xx+ (diff) | |
| download | kernel-qcow2-linux-109e2381749c1cfd94a0d22b2b54142539024973.tar.gz kernel-qcow2-linux-109e2381749c1cfd94a0d22b2b54142539024973.tar.xz kernel-qcow2-linux-109e2381749c1cfd94a0d22b2b54142539024973.zip | |
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 <roland@purestorage.com>
Signed-off-by: Spencer Baugh <sbaugh@catern.com>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Diffstat (limited to 'drivers/target/iscsi/iscsi_target_tpg.c')
0 files changed, 0 insertions, 0 deletions