All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Designing a new prio_callout
Date: Mon, 30 Jul 2007 08:31:01 +0200	[thread overview]
Message-ID: <46AD85A5.1060609@suse.de> (raw)
In-Reply-To: <d61540a40707290903q359cc7c8g52f07627b4b9fba7@mail.gmail.com>

Ethan John wrote:
> Thanks for the heads-up about ALUA. We're looking into it.
> 
> What is the purpose of the custom mpio_prio_* applications that ship
> with open-iscsi if not to handle multipathing?
> 
It is. mpath_prio_* are the priority callouts for multipathing.
They determine the layout of the multipath map.
Theory is that mpath_prio_* will return the priority for a
given path in relation to the entire multipath layout.

If used with 'group_by_prio' all paths with the same
priority will be grouped into one multipath group, and
the group with the highest priority will become active.

When all paths in a group fail, the group with the next
highest priority will become active. Additionally some
failover command (as determined by the hardware handler)
may be send to the target.

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)

  reply	other threads:[~2007-07-30  6:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 21:42 Designing a new prio_callout Ethan John
2007-07-25 11:37 ` Hannes Reinecke
2007-07-29 16:03   ` Ethan John
2007-07-30  6:31     ` Hannes Reinecke [this message]
2007-08-09 17:55       ` Ethan John
2007-08-10 15:07         ` Hannes Reinecke
2007-08-10 15:40           ` Ethan John
2007-08-14 17:05             ` Ethan John
2007-08-15  8:45               ` Stefan Bader
2007-08-15 15:57                 ` Ethan John
2007-08-16 10:58                   ` Stefan Bader
2007-08-16 17:30                     ` Ethan John
2007-08-27 15:09               ` Hannes Reinecke
2007-08-27 15:50                 ` Ethan John

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=46AD85A5.1060609@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.