From: Martin Wilck <mwilck@suse.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: dm-devel@redhat.com, Xose Vazquez Perez <xose.vazquez@gmail.com>
Subject: [PATCH 0/2] multipath-tools: hwhandler autodetection
Date: Tue, 27 Mar 2018 23:50:51 +0200 [thread overview]
Message-ID: <20180327215053.3631-1-mwilck@suse.com> (raw)
This is patch set is a follow-up of the late discussion
"Can we drop 'hardware_handler "1 alua"'?". With patch 1/2 in place,
I think we can - multipath uses the TPGS flag to determine whether
or not the paths support ALUA, and sets the hwhandler accordingly.
Unlike the "detect_checker" and "detect_prio" options, I have coded this
so that explicit "hardware_hander" settings take priority over autodetection,
except for the case in which we determine that TPGS is unsupported.
Thus I don't think an additional "detect_hwhandler" config option is
necessary.
To be actually effective to solve the problems with certain types of IBM IPR
controllers, patch 1/2 must be combined with my previous
patch "libmultipath: don't reject maps with undefined prio".
Patch 2/2 is just a cleanup that looked logical to do after 1/2.
Martin Wilck (2):
libmultipath: hwhandler auto-detection for ALUA
libmultipath/propsel: (re)use static const vars for origin
libmultipath/propsel.c | 187 ++++++++++++++++++++++++++++++-------------------
1 file changed, 114 insertions(+), 73 deletions(-)
--
2.16.1
next reply other threads:[~2018-03-27 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 21:50 Martin Wilck [this message]
2018-03-27 21:50 ` [PATCH 1/2] libmultipath: hwhandler auto-detection for ALUA Martin Wilck
2018-04-03 20:31 ` Benjamin Marzinski
2018-04-03 20:53 ` Martin Wilck
2018-04-03 21:29 ` Benjamin Marzinski
2018-04-04 8:04 ` Martin Wilck
2018-04-12 15:43 ` Martin Wilck
2018-04-12 19:49 ` Benjamin Marzinski
2018-04-04 6:38 ` Hannes Reinecke
2018-03-27 21:50 ` [PATCH 2/2] libmultipath/propsel: (re)use static const vars for origin Martin Wilck
2018-03-28 19:11 ` Benjamin Marzinski
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=20180327215053.3631-1-mwilck@suse.com \
--to=mwilck@suse.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox