All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: feature="1 queue_if_no_path" vs. no_path_retry=queue
Date: Tue, 20 Sep 2011 12:05:00 +0900	[thread overview]
Message-ID: <4E7802DC.5090009@ct.jp.nec.com> (raw)
In-Reply-To: <20110916224737.GB31898@orenhe-laptop>

Hi,

Oren Held wrote:
> Hi,
> 
> According to all docs I've read, and some code, the following settings seem to have the same effect:
> 1. Setting features = "1 queue_if_no_path"
> 2. Setting no_path_retry = "queue"
> 
> Now that's confusing, especially when having conflicting configuration, e.g., from hwtable.c:
>                 /* IBM DS4100 */
>                 .vendor        = "IBM",
>                 .product       = "1724",
>                 .features      = "1 queue_if_no_path",
>                 .no_path_retry = 300,
> 
> It's not clear enough what would be the resulting behavior of this configuration.
> 
> Did I get it right? Is there a reason for keeping the features = "1 queue_if_no_path" option available in multipath-tools?

See http://marc.info/?l=dm-devel&m=124572577028515&w=2

Thanks,
Kiyoshi Ueda


> Thanks
> 
> Regards
> 
> - Oren

      reply	other threads:[~2011-09-20  3:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 22:47 feature="1 queue_if_no_path" vs. no_path_retry=queue Oren Held
2011-09-20  3:05 ` Kiyoshi Ueda [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=4E7802DC.5090009@ct.jp.nec.com \
    --to=k-ueda@ct.jp.nec.com \
    --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.