Re: [dm-devel] [PATCH 1/2] multipath.conf(5): remove io-affinity information

2022-12-07 Thread Mike Christie
On 12/3/22 9:10 AM, Xose Vazquez Perez wrote: > On 11/30/22 05:56, bmarzins at redhat.com (Benjamin Marzinski) wrote: > >> 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

Re: [dm-devel] [PATCH 1/2] multipath.conf(5): remove io-affinity information

2022-12-03 Thread Xose Vazquez Perez
On 11/30/22 05:56, bmarzins at redhat.com (Benjamin Marzinski) wrote: 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 bitmap of CPUs that a path can run on. This

Re: [dm-devel] [PATCH 1/2] multipath.conf(5): remove io-affinity information

2022-11-30 Thread Martin Wilck
On Tue, 2022-11-29 at 22:56 -0600, Benjamin Marzinski wrote: > 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 bitmap of CPUs that a path can > run > on. This

[dm-devel] [PATCH 1/2] multipath.conf(5): remove io-affinity information

2022-11-29 Thread Benjamin Marzinski
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 bitmap of CPUs that a path can run on. This isn't something that lends itself to the kind of auto-assembling that