From: Hannes Reinecke <hare@suse.de>
To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Cc: device-mapper development <dm-devel@redhat.com>,
"linux-scsi@vger.kernel.org" <Linux-scsi@vger.kernel.org>
Subject: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
Date: Wed, 13 Jan 2016 10:10:43 +0100 [thread overview]
Message-ID: <56961493.5010901@suse.de> (raw)
Hi all,
I'd like to attend LSF/MM and would like to present my ideas for a
multipath redesign.
The overall idea is to break up the centralized multipath handling
in device-mapper (and multipath-tools) and delegate to the
appropriate sub-systems.
Individually the plan is:
a) use the 'wwid' sysfs attribute to detect multipath devices;
this removes the need of the current 'path_id' functionality
in multipath-tools
b) leverage topology information from scsi_dh_alua (which we will
have once my ALUA handler update is in) to detect the multipath
topology. This removes the need of a 'prio' infrastructure
in multipath-tools
c) implement block or scsi events whenever a remote port becomes
unavailable. This removes the need of the 'path_checker'
functionality in multipath-tools.
d) leverage these events to handle path-up/path-down events
in-kernel
e) move the I/O redirection logic out of device-mapper proper
and use blk-mq to redirect I/O. This is still a bit of
hand-waving, and definitely would need discussion to figure
out if and how it can be achieved.
This is basically the same topic Mike Snitzer proposed, but
coming from a different angle.
But in the end we should be able to do strip down the current
(rather complex) multipath-tools to just handle topology changes;
everything else will be done internally.
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-01-13 9:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 9:10 Hannes Reinecke [this message]
2016-01-13 10:50 ` [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign Sagi Grimberg
2016-01-13 10:50 ` Sagi Grimberg
2016-01-13 11:46 ` Hannes Reinecke
2016-01-13 11:46 ` Hannes Reinecke
2016-01-13 15:42 ` Mike Snitzer
2016-01-13 15:42 ` Mike Snitzer
2016-01-13 16:06 ` Sagi Grimberg
2016-01-13 16:06 ` Sagi Grimberg
2016-01-13 16:21 ` Mike Snitzer
2016-01-13 16:21 ` Mike Snitzer
2016-01-13 16:30 ` Sagi Grimberg
2016-01-13 16:30 ` Sagi Grimberg
2016-01-13 16:18 ` Hannes Reinecke
2016-01-13 16:18 ` Hannes Reinecke
2016-01-13 16:54 ` Mike Snitzer
2016-01-13 16:54 ` Mike Snitzer
2016-01-13 11:08 ` [dm-devel] " Alasdair G Kergon
2016-01-13 11:17 ` Hannes Reinecke
2016-01-13 11:25 ` Alasdair G Kergon
2016-01-13 17:52 ` Benjamin Marzinski
2016-01-14 7:25 ` Hannes Reinecke
2016-01-14 19:09 ` Bart Van Assche
2016-01-15 7:12 ` Hannes Reinecke
2016-01-21 0:38 ` 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=56961493.5010901@suse.de \
--to=hare@suse.de \
--cc=Linux-scsi@vger.kernel.org \
--cc=dm-devel@redhat.com \
--cc=lsf-pc@lists.linux-foundation.org \
/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.