From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Brian Bunker <brian@purestorage.com>,
Martin Wilck <mwilck@suse.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
DM-DEVEL ML <dm-devel@lists.linux.dev>
Subject: Re: [PATCH 0/1] pr: add alua path checker
Date: Fri, 13 Mar 2026 01:43:08 +0100 [thread overview]
Message-ID: <8491dc36-0e80-4c2a-bb89-4a8cdcaa3a79@gmail.com> (raw)
In-Reply-To: <20260312001642.53321-1-brian@purestorage.com>
On 3/12/26 1:16 AM, Brian Bunker wrote:
> For ALUA-capable storage arrays, multipath-tools currently uses TUR
> (Test Unit Ready) as the default path checker while a separate
> prioritizer determines ALUA state. When sysfs provides ALUA state
> (the common case), no RTPG command is needed for priority. However,
> if sysfs is unavailable or detect_prio is off, the prioritizer issues
> RTPG, resulting in two SCSI commands per path check cycle: TUR + RTPG.
prio/checker changes should be documented in multipath/multipath.conf.5.in
Thanks.
prev parent reply other threads:[~2026-03-13 0:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 0:16 [PATCH 0/1] checkers: add alua path checker Brian Bunker
2026-03-12 0:16 ` [PATCH 1/1] " Brian Bunker
2026-03-12 16:32 ` Martin Wilck
[not found] ` <CAHZQxy+V5YSiHnB5sp8A_jbN_n1OQ633KiDeFa+vXQrNafHzDA@mail.gmail.com>
2026-03-12 19:31 ` Martin Wilck
2026-03-12 19:33 ` Brian Bunker
2026-03-13 0:34 ` Xose Vazquez Perez
2026-03-15 2:37 ` Benjamin Marzinski
2026-03-12 7:10 ` [PATCH 0/1] " Hannes Reinecke
2026-03-12 16:48 ` Martin Wilck
2026-03-12 21:05 ` Xose Vazquez Perez
2026-03-12 19:19 ` Brian Bunker
2026-03-13 0:43 ` Xose Vazquez Perez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8491dc36-0e80-4c2a-bb89-4a8cdcaa3a79@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=bmarzins@redhat.com \
--cc=brian@purestorage.com \
--cc=dm-devel@lists.linux.dev \
--cc=mwilck@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox