From: Hannes Reinecke <hare@suse.de>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: dm-devel@redhat.com, Christophe Varoqui <christophe.varoqui@gmail.com>
Subject: Re: multipathd: Add 'sysfs' prioritizer
Date: Fri, 3 Jun 2016 09:05:57 +0200 [thread overview]
Message-ID: <57512C55.2010008@suse.de> (raw)
In-Reply-To: <20160531223414.00004376@localhost>
On 05/31/2016 10:34 PM, Sebastian Herbszt wrote:
> Hannes Reinecke wrote:
>> Recent kernels have an 'access_state' attribute which allows
>> us to read the asymmetric access state directly from sysfs.
>>
>> Signed-off-by: Hannes Reinecke <hare@suse.de>
>> ---
>> libmultipath/discovery.c | 33 +++++++++++++++++++++++++++++
>> libmultipath/discovery.h | 2 ++
>> libmultipath/prio.h | 1 +
>> libmultipath/prioritizers/Makefile | 3 ++-
>> libmultipath/prioritizers/sysfs.c | 43 ++++++++++++++++++++++++++++++++++++++
>> libmultipath/propsel.c | 6 +++++-
>> multipath/multipath.conf.5 | 14 ++++++++++++-
>> 7 files changed, 99 insertions(+), 3 deletions(-)
>> create mode 100644 libmultipath/prioritizers/sysfs.c
>
> How about just adding this to the alua prioritizer?
> This new feature could then depend on a "sysfs" argument.
>
No. The 'sysfs' prioritizer is using the abstract kernel sysfs
interface, for which every device handler provides the information.
So in theory it's independent on the underlying device handler.
However, only the ALUA device handler has been reworked to provide
up-to-date information; for the other device handlers there is a
risk of the sysfs information is getting out-of-date.
Hence I've restricted the 'detect_prioritizer' algorithm to select
'sysfs' only if an ALUA system is present.
But this doesn't imply in any way that the 'sysfs' prioritizer can be
used only for ALUA systems.
Christophe, what about merging the patch?
Cheers,
Hannes
next prev parent reply other threads:[~2016-06-03 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 10:20 multipathd: Add 'sysfs' prioritizer Hannes Reinecke
2016-05-24 17:06 ` Benjamin Marzinski
2016-05-31 20:34 ` Sebastian Herbszt
2016-06-03 7:05 ` Hannes Reinecke [this message]
2016-06-03 7:24 ` Christophe Varoqui
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=57512C55.2010008@suse.de \
--to=hare@suse.de \
--cc=christophe.varoqui@gmail.com \
--cc=dm-devel@redhat.com \
--cc=herbszt@gmx.de \
/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.