From: Hannes Reinecke <hare@suse.de>
To: Mike Snitzer <snitzer@redhat.com>,
"Stewart, Sean" <Sean.Stewart@netapp.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Bryn Reeves <breeves@redhat.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: dm-multipath: Accept failed paths for multipath maps
Date: Fri, 18 Jul 2014 08:00:48 +0200 [thread overview]
Message-ID: <53C8B810.2060206@suse.de> (raw)
In-Reply-To: <20140718002319.GA20071@redhat.com>
On 07/18/2014 02:23 AM, Mike Snitzer wrote:
> On Thu, Jul 17 2014 at 8:04pm -0400,
> Mike Snitzer <snitzer@redhat.com> wrote:
>
>> Revisiting this can of worms...
>>
>> As part of full due-diligence on the approach that SUSE and NetApp have
>> seemingly enjoyed "for years" I reviewed Hannes' v3 patch, fixed one
>> issue and did some cleanup. I then converted over to using a slightly
>> different approach where-in the DM core becomes a more willing
>> co-conspirator in this hack by introducing the ability to have
>> place-holder devices (dm_dev without an opened bdev) referenced in a DM
>> table. The work is here:
>> http://git.kernel.org/cgit/linux/kernel/git/snitzer/linux.git/log/?h=throwaway-dm-mpath-placeholder-devs
>
> Here is the rolled up patch (the individual commits in the above branch
> are rather noisy given the sequencing):
>
> drivers/md/dm-mpath.c | 51 +++++++++++++++++++++++++++++++++----------------
> drivers/md/dm-table.c | 53 ++++++++++++++++++++++++++++++++++++++-------------
> drivers/md/dm.c | 5 ++---
> drivers/md/dm.h | 12 ++++++++++++
> 4 files changed, 89 insertions(+), 32 deletions(-)
>
These patches look quite okay; I'll be cross-checking with my
version and do some testing there.
Will be sending some update once the testing is done.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2014-07-18 6:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 7:52 [PATCHv2] dm-multipath: Accept failed paths for multipath maps Hannes Reinecke
2013-12-18 14:08 ` Mike Snitzer
2013-12-18 14:25 ` Hannes Reinecke
2013-12-18 15:28 ` Stewart, Sean
2013-12-19 8:21 ` Bart Van Assche
2014-02-19 1:14 ` Mike Snitzer
2014-02-19 8:11 ` Bart Van Assche
2014-07-18 0:04 ` Mike Snitzer
2014-07-18 0:23 ` Mike Snitzer
2014-07-18 6:00 ` Hannes Reinecke [this message]
2014-07-18 16:04 ` Mike Snitzer
2014-07-18 16:15 ` Mike Snitzer
2014-07-21 6:05 ` Hannes Reinecke
2014-07-18 0:29 ` John Utz
2014-07-18 2:18 ` Mike Snitzer
2014-07-18 3:31 ` John Utz
2014-07-18 5:57 ` Hannes Reinecke
2014-07-18 14:38 ` Mike Snitzer
2014-07-18 17:04 ` John Utz
2014-07-21 14:23 ` ZAC target (Was: Re: dm-multipath: Accept failed paths for multipath maps) Hannes Reinecke
2014-07-21 19:28 ` Kent Overstreet
2014-07-22 5:46 ` Hannes Reinecke
2014-07-22 8:08 ` Matias Bjorling
2014-07-18 16:51 ` dm-multipath: Accept failed paths for multipath maps John Utz
2014-07-18 6:12 ` Hannes Reinecke
2013-12-18 15:28 ` Merla, ShivaKrishna
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=53C8B810.2060206@suse.de \
--to=hare@suse.de \
--cc=Sean.Stewart@netapp.com \
--cc=agk@redhat.com \
--cc=breeves@redhat.com \
--cc=dm-devel@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox