summaryrefslogtreecommitdiffstats
path: root/include/scsi
diff options
context:
space:
mode:
authorMike Christie <michael.christie@oracle.com>2023-08-17 14:29:02 -0500
committerMartin K. Petersen <martin.petersen@oracle.com>2023-08-21 17:20:48 -0400
commit84c073fd89de22d5cb09edffb1f692a1964fd584 (patch)
tree747a7abdff001d5a0ff0b65584a2cad5e7193ee2 /include/scsi
parent19d7102a953900560811498018bb2de4e27ee9d9 (diff)
downloadlinux-84c073fd89de22d5cb09edffb1f692a1964fd584.tar.gz
linux-84c073fd89de22d5cb09edffb1f692a1964fd584.tar.bz2
linux-84c073fd89de22d5cb09edffb1f692a1964fd584.zip
scsi: target: Fix write perf due to unneeded throttling
The write back throttling (WBT) code checks if REQ_SYNC | REQ_IDLE is set to determine if a write is O_DIRECT vs buffered. If the bits are not set then it assumes it's a buffered write and will throttle LIO if we hit certain metrics. LIO itself is not using the buffer cache and is doing direct I/O, so this has us set the direct bits so we are not throttled. When the initiator application is doing direct I/O this can greatly improve performance. It depends on the backend device but we have seen where the WBT code is throttling writes to only 20K IOPs with 4K I/Os when the device can support 100K+. Signed-off-by: Mike Christie <michael.christie@oracle.com> Link: https://lore.kernel.org/r/20230817192902.346791-1-michael.christie@oracle.com Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'include/scsi')
0 files changed, 0 insertions, 0 deletions