From 34da69561285c243f00a685e6c0d3dbeda1ef2b6 Mon Sep 17 00:00:00 2001 From: Benjamin Marzinski Date: Wed, 30 Nov 2022 15:28:42 -0600 Subject: [PATCH] device-mapper-multipath-0.8.7-16 Add 0076-multipath.conf-5-remove-io-affinity-information.patch Resolves: bz #2143125 --- ...onf-5-remove-io-affinity-information.patch | 33 +++++++++++++++++++ device-mapper-multipath.spec | 7 +++- 2 files changed, 39 insertions(+), 1 deletion(-) create mode 100644 0076-multipath.conf-5-remove-io-affinity-information.patch diff --git a/0076-multipath.conf-5-remove-io-affinity-information.patch b/0076-multipath.conf-5-remove-io-affinity-information.patch new file mode 100644 index 0000000..9123625 --- /dev/null +++ b/0076-multipath.conf-5-remove-io-affinity-information.patch @@ -0,0 +1,33 @@ +From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001 +From: Benjamin Marzinski +Date: Tue, 29 Nov 2022 19:56:37 -0600 +Subject: [PATCH] multipath.conf(5): remove io-affinity information + +The multpath-tools do not support the io-affinity path selector. We +always add a repeat count as the path argument. The io-affinity selector +doesn't take one. Instead it takes a bit map of CPUs that a path can +run on. This isn't something that lends itself to the kind of +auto-assembling that multipathd does. But even if we did want to +try to support this path-selector, until we do, we shouldn't be listing +it in the multipath.conf documentation. + +Signed-off-by: Benjamin Marzinski +--- + multipath/multipath.conf.5 | 4 ---- + 1 file changed, 4 deletions(-) + +diff --git a/multipath/multipath.conf.5 b/multipath/multipath.conf.5 +index 01904feb..5e447e67 100644 +--- a/multipath/multipath.conf.5 ++++ b/multipath/multipath.conf.5 +@@ -211,10 +211,6 @@ of outstanding I/O to the path and its relative throughput. + estimation of future service time based on the history of previous I/O submitted + to each path. + .TP +-.I "io-affinity 0" +-(Since 5.11 kernel) Choose the path for the next bunch of I/O based on a CPU to +-path mapping the user passes in and what CPU we are executing on. +-.TP + The default is: \fBservice-time 0\fR + .RE + . diff --git a/device-mapper-multipath.spec b/device-mapper-multipath.spec index 53386c6..2fa73b7 100644 --- a/device-mapper-multipath.spec +++ b/device-mapper-multipath.spec @@ -1,6 +1,6 @@ Name: device-mapper-multipath Version: 0.8.7 -Release: 15%{?dist} +Release: 16%{?dist} Summary: Tools to manage multipath devices using device-mapper License: GPLv2 URL: http://christophe.varoqui.free.fr/ @@ -85,6 +85,7 @@ Patch0072: 0072-multipath-tests-tests-for-reconcile_features_with_qu.patch Patch0073: 0073-libmultipath-prepare-proto_id-for-use-by-non-scsi-de.patch Patch0074: 0074-libmultipath-get-nvme-path-transport-protocol.patch Patch0075: 0075-libmultipath-enforce-queue_mode-bio-for-nmve-tcp-pat.patch +Patch0076: 0076-multipath.conf-5-remove-io-affinity-information.patch # runtime @@ -287,6 +288,10 @@ fi %{_pkgconfdir}/libdmmp.pc %changelog +* Wed Nov 30 2022 Benjamin Marzinski - 0.8.7-16 +- Add 0076-multipath.conf-5-remove-io-affinity-information.patch +- Resolves: bz #2143125 + * Thu Nov 10 2022 Benjamin Marzinski - 0.8.7-15 - Add 0067-kpartx-hold-device-open-until-partitions-have-been-c.patch * Fixes bz #2141860