From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] multipath-tools: Add preferred TPG prioritizer
Date: Mon, 14 Sep 2009 08:24:39 +0200 [thread overview]
Message-ID: <4AADE1A7.1080008@suse.de> (raw)
In-Reply-To: <20090911182308.GN15326@ether.msp.redhat.com>
Benjamin Marzinski wrote:
> Instead of using the Target port's Asymmetric Access State to determine
> priority, some users what to use the preferred port bit. This patch makes
> a new prioritizer, based off the ALUA prioritizer, but using the preferred
> port bit instead.
>
Please, no.
This would mean that 'tpg_pref' would evaluate the PREF bit _only_,
with total disregard to the other settings.
We should be updating the existing 'alua' prioritizer to evaluate
the PREF bit together with the existing AAS status; then we could
be using it for all scenarios.
I think I got a patch somewhere ...
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2009-09-14 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 18:23 [PATCH] multipath-tools: Add preferred TPG prioritizer Benjamin Marzinski
2009-09-14 6:24 ` Hannes Reinecke [this message]
2009-09-14 15:59 ` 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=4AADE1A7.1080008@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox