From: Benjamin Marzinski <bmarzins@redhat.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Martin Wilck <mwilck@suse.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>,
DM-DEVEL ML <dm-devel@lists.linux.dev>
Subject: Re: [PATCH RFC] multipath-tools: add Generic SCSI in hwtable
Date: Mon, 17 Mar 2025 16:00:54 -0400 [thread overview]
Message-ID: <Z9h_dgeRCakpLak9@redhat.com> (raw)
In-Reply-To: <20250317173352.14387-1-xose.vazquez@gmail.com>
On Mon, Mar 17, 2025 at 06:33:51PM +0100, Xose Vazquez Perez wrote:
> Cc: Martin Wilck <mwilck@suse.com>
> Cc: Benjamin Marzinski <bmarzins@redhat.com>
> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
> Cc: DM-DEVEL ML <dm-devel@lists.linux.dev>
> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
> ---
> libmultipath/hwtable.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
> index f8cf3fa9..34b1fd2f 100644
> --- a/libmultipath/hwtable.c
> +++ b/libmultipath/hwtable.c
> @@ -79,6 +79,17 @@
> #endif
>
If we wanted to make these changes, we could just change
DEFAULT_PGPOLICY, DEFAULT_FAILBACK, and DEFAULT_NO_PATH_RETRY. But I
still think that for completely unknown devices, we should stick with
our current defaults. They're safe and I haven't heard any complaints
about them.
-Ben
> static struct hwentry default_hw[] = {
> + /*
> + * Generic SCSI devices
> + */
> + {
> + /* Generic SCSI */
> + .vendor = ".*",
> + .product = ".*",
> + .pgpolicy = GROUP_BY_PRIO,
> + .pgfailback = -FAILBACK_IMMEDIATE,
> + .no_path_retry = 30,
> + },
> /*
> * Generic NVMe devices
> *
> --
> 2.48.1
next prev parent reply other threads:[~2025-03-17 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 17:33 [PATCH RFC] multipath-tools: add Generic SCSI in hwtable Xose Vazquez Perez
2025-03-17 20:00 ` Benjamin Marzinski [this message]
2025-03-18 11:08 ` Martin Wilck
2025-03-18 23:32 ` Benjamin Marzinski
2025-03-19 10:06 ` Martin Wilck
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=Z9h_dgeRCakpLak9@redhat.com \
--to=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=mwilck@suse.com \
--cc=xose.vazquez@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.