From: Hannes Reinecke <hare@suse.de>
To: linux-scsi@vger.kernel.org
Cc: dm-devel@redhat.com, Mike Snitzer <snitzer@redhat.com>,
Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/2] 'default' hardware handler for multipath
Date: Mon, 2 Apr 2012 18:43:53 +0200 [thread overview]
Message-ID: <1333385035-6663-1-git-send-email-hare@suse.de> (raw)
This patchset introduces a 'default' hardware handler for
dm-multipath.
Modern storage arrays typically support two failover methods,
the original proprietary and the modern ALUA-based one.
The device_handler implementation will currently select the
ALUA handler, and falling back to the proprietary one if
ALUA isn't supported.
However, in the built-in hardware table for multipath one
can specify only one hardware handler, causing the original
hardware handler to be overwritten.
By specifying a 'default' hardware handler multipath will not
try to attach a specific hardware handler, but rather using
the currently attached on.
Hannes Reinecke (2):
scsi_dh: Allow NULL hardware handler name in scsi_dh_attach()
dm-mpath: Allow 'default' hardware handler
drivers/md/dm-mpath.c | 8 ++++++--
drivers/scsi/device_handler/scsi_dh.c | 8 ++++++--
2 files changed, 12 insertions(+), 4 deletions(-)
--
1.7.7
next reply other threads:[~2012-04-02 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 16:43 Hannes Reinecke [this message]
2012-04-02 16:43 ` [PATCH 1/2] scsi_dh: Allow NULL hardware handler name in scsi_dh_attach() Hannes Reinecke
2012-04-02 17:06 ` Mike Snitzer
2012-04-03 1:46 ` [dm-devel] " Jun'ichi Nomura
2012-04-02 16:43 ` [PATCH 2/2] dm-mpath: Allow 'default' hardware handler Hannes Reinecke
2012-04-02 17:04 ` Mike Snitzer
2012-04-02 17:07 ` Hannes Reinecke
2012-04-03 1:45 ` [dm-devel] " Jun'ichi Nomura
2012-04-03 21:12 ` [dm-devel] [PATCH 0/2] 'default' hardware handler for multipath Moger, Babu
2012-04-18 14:07 ` Hannes Reinecke
2012-04-18 16:25 ` Moger, Babu
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=1333385035-6663-1-git-send-email-hare@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=snitzer@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.