All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Herbszt <herbszt@gmx.de>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [PATCH] multipath-tools: add FUJITSU/ETERNUS 2000/4000/8000 to hwtable
Date: Sat, 8 Oct 2016 22:30:49 +0200	[thread overview]
Message-ID: <20161008223049.00006901@gmx.de> (raw)
In-Reply-To: <20161005211252.9761-1-xose.vazquez@gmail.com>

Vazquez Perez wrote:
> Based on documentation provided by the manufacturer:
> http://storage-system.fujitsu.com/global/manual/diskarray/pdf/p3am-3192-en.pdf
> 
> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
> Cc: device-mapper development <dm-devel@redhat.com>
> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
> ---
>  libmultipath/hwtable.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
> index e1ed7ef..367aa0a 100644
> --- a/libmultipath/hwtable.c
> +++ b/libmultipath/hwtable.c
> @@ -268,6 +268,14 @@ static struct hwentry default_hw[] = {
>  		.product       = "FC2502",
>  		.pgpolicy      = MULTIBUS,
>  	},
> +	{
> +		.vendor        = "FUJITSU",
> +		.product       = "E[248]000",
> +		.pgpolicy      = GROUP_BY_PRIO,
> +		.pgfailback    = -FAILBACK_IMMEDIATE,
> +		.no_path_retry = 10,
> +		.prio_name     = PRIO_ALUA,
> +	},
>  	/*
>  	 * Hitachi
>  	 *

Now that you dropped the path selector as suggested back in July [1]
why not merge this with the ETERNUS DX entry?

[1] https://www.redhat.com/archives/dm-devel/2016-July/msg00595.html

Sebastian

  reply	other threads:[~2016-10-08 20:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 21:12 [PATCH] multipath-tools: add FUJITSU/ETERNUS 2000/4000/8000 to hwtable Xose Vazquez Perez
2016-10-08 20:30 ` Sebastian Herbszt [this message]
2016-10-22 21:27   ` Xose Vazquez Perez

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=20161008223049.00006901@gmx.de \
    --to=herbszt@gmx.de \
    --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 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.