summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorGuixin Liu <kanie@linux.alibaba.com>2024-12-09 04:53:44 +0300
committerKeith Busch <kbusch@kernel.org>2025-01-07 19:05:19 +0300
commit3ec5c62cfcf060e9ea533cd3901f5d03b26ddc24 (patch)
treea1725ebc8804e7185e8e0a82981690c135634faf /tools/perf/scripts/python/export-to-postgresql.py
parent844b8cdc681612ff24df62cdefddeab5772fadf1 (diff)
downloadlinux-3ec5c62cfcf060e9ea533cd3901f5d03b26ddc24.tar.xz
nvmet: handle rw's limited retry flag
In some scenarios, some multipath software setup places the REQ_FAILFAST_DEV flag on I/O to prevent retries and immediately switch to other paths for issuing I/O commands. This will reflect on the NVMe read and write commands with the limited retry flag. However, the current NVMe target side does not handle the limited retry flag, and the target's underlying driver still retries the I/O. This will result in the I/O not being quickly switched to other paths, ultimately leading to increased I/O latency. When the nvme target receive an rw command with limited retry flag, handle it in block backend by setting the REQ_FAILFAST_DEV flag to bio. Signed-off-by: Guixin Liu <kanie@linux.alibaba.com> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Sagi Grimberg <sagi@grimberg.me> Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions