Roland Dreier 109e238174 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>		2015-08-02 23:11:52 -07:00
..
iscsi	target: Drop iSCSI use of mutex around max_cmd_sn increment	2015-08-02 23:11:52 -07:00
configfs_macros.h	doc: fix broken references	2011-09-27 18:08:04 +02:00
target_core_backend.h	target: Return descriptor format sense data in case the LU spans 64bit sectors	2015-07-23 22:54:21 -07:00
target_core_base.h	target: Shrink struct se_cmd by rearranging fields	2015-07-31 00:10:33 -07:00
target_core_fabric_configfs.h	target: Add target_show_dynamic_sessions attribute helper	2015-03-06 21:24:53 -08:00
target_core_fabric.h	tcm_loop: Send I_T_NEXUS_LOSS_OCCURRED UA	2015-07-23 22:08:22 -07:00