Blame SOURCES/0076-multipath.conf-5-remove-io-affinity-information.patch

e71b65
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
e71b65
From: Benjamin Marzinski <bmarzins@redhat.com>
e71b65
Date: Tue, 29 Nov 2022 19:56:37 -0600
e71b65
Subject: [PATCH] multipath.conf(5): remove io-affinity information
e71b65
e71b65
The multpath-tools do not support the io-affinity path selector.  We
e71b65
always add a repeat count as the path argument. The io-affinity selector
e71b65
doesn't take one. Instead it takes a bit map of CPUs that a path can
e71b65
run on. This isn't something that lends itself to the kind of
e71b65
auto-assembling that multipathd does. But even if we did want to
e71b65
try to support this path-selector, until we do, we shouldn't be listing
e71b65
it in the multipath.conf documentation.
e71b65
e71b65
Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
e71b65
---
e71b65
 multipath/multipath.conf.5 | 4 ----
e71b65
 1 file changed, 4 deletions(-)
e71b65
e71b65
diff --git a/multipath/multipath.conf.5 b/multipath/multipath.conf.5
e71b65
index 01904feb..5e447e67 100644
e71b65
--- a/multipath/multipath.conf.5
e71b65
+++ b/multipath/multipath.conf.5
e71b65
@@ -211,10 +211,6 @@ of outstanding I/O to the path and its relative throughput.
e71b65
 estimation of future service time based on the history of previous I/O submitted
e71b65
 to each path.
e71b65
 .TP
e71b65
-.I "io-affinity 0"
e71b65
-(Since 5.11 kernel) Choose the path for the next bunch of I/O based on a CPU to
e71b65
-path mapping the user passes in and what CPU we are executing on.
e71b65
-.TP
e71b65
 The default is: \fBservice-time 0\fR
e71b65
 .RE
e71b65
 .