diff options
| author | Douglas Gilbert <dgilbert@interlog.com> | 2022-01-08 20:28:50 -0500 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2022-01-25 00:25:06 -0500 |
| commit | 7109f3701a4a6e4eef556c1707a361bed25813b3 (patch) | |
| tree | e73416a814872637570da54a91e3c466feb4f473 /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | 500d0d24808138cf95a785c7f4e51b2841974193 (diff) | |
| download | linux-7109f3701a4a6e4eef556c1707a361bed25813b3.tar.gz linux-7109f3701a4a6e4eef556c1707a361bed25813b3.zip | |
scsi: scsi_debug: Add no_rwlock parameter
By default, this driver places a read lock around all user data fetches and
a write lock around all user data modifying operations (e.g. WRITE
commands). These locks have "per store" granularity. Other drivers that
have a similar function (e.g. null_blk) do not take this data integrity
step and run significantly faster in some tests.
In the common case of a (simulated) device to device copy (e.g. what dd
and its variants do) there should be no need for locks around data
accesses. So add the driver and sysfs parameter no_rwlock which is boolean
and when set does what its name suggests. The default is false for backward
comaptibility.
Link: https://lore.kernel.org/r/20220109012853.301953-7-dgilbert@interlog.com
Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions
