diff options
| author | John Garry <john.g.garry@oracle.com> | 2025-02-24 11:55:14 +0000 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2025-02-24 20:53:07 -0500 |
| commit | 2af3b0c1082bd9365faf0a6c82264d09fe081f33 (patch) | |
| tree | 64740b02837963f827229f5117645ca6f3c675ac /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 0107fb8686b289f6685e9d9cc205616e100f2327 (diff) | |
scsi: scsi_debug: Remove sdebug_device_access_info
This structure is not used, so delete it.
It was originally intended for supporting checking for atomic writes
overlapping with ongoing reads and writes, but that support never got
added.
SBC-4 r22 section 4.29.3.2 "Performing operations during an atomic write
operation" describes two methods of handling overlapping atomic writes.
Currently the only method supported is for the ongoing read or write to
complete.
Signed-off-by: John Garry <john.g.garry@oracle.com>
Link: https://lore.kernel.org/r/20250224115517.495899-2-john.g.garry@oracle.com
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions