From: Hannes Reinecke <hare@suse.de>
To: dm-devel@redhat.com
Subject: Re: [PATCH v2] multipath: add detect_prio option to autodetect prioitizer
Date: Mon, 14 Jan 2013 08:02:10 +0100 [thread overview]
Message-ID: <50F3AD72.5070109@suse.de> (raw)
In-Reply-To: <1357993580.4263.5.camel@lapoo.opensvc.com>
On 01/12/2013 01:26 PM, Christophe Varoqui wrote:
> On ven., 2013-01-11 at 08:17 +0100, Hannes Reinecke wrote:
>> On 01/10/2013 09:13 PM, Benjamin Marzinski wrote:
>>> This patch adds a new multipath.conf option, detect_prio. If set to yes,
>>> multipathd will try to determine the correct prioritizer for the device. If
>>> it finds one, that will be used instead of its configured prioritizer. If
>>> none is found, the configured prioritizer will be used. It can currently
>>> only detect ALUA devices.
>>>
>>> Also fixed and issue with select_prio where in the devices section, it was
>>> passing in the prio name string instead of the prio args string to prio_get()
>>>
>>> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
>>
>> Good idea.
>>
> Don"t you think it would be fair to fallback to autodetection if no
> prioritizer is set, instead ? Admins would expect the values they care
> to set in the config file are honored.
>
It would, if we had autodetection for more (or, better, all)
hardware handlers.
Shouldn't be too hard.
I'll give it a go at it once this patchset is merged.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
prev parent reply other threads:[~2013-01-14 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 20:13 [PATCH v2] multipath: add detect_prio option to autodetect prioitizer Benjamin Marzinski
2013-01-11 7:17 ` Hannes Reinecke
2013-01-12 12:26 ` Christophe Varoqui
2013-01-14 7:02 ` Hannes Reinecke [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=50F3AD72.5070109@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.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.