From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: good dm-mpath test setup?
Date: Thu, 05 Jun 2014 14:17:10 +0200 [thread overview]
Message-ID: <53905FC6.5030006@suse.de> (raw)
In-Reply-To: <20140605115011.GA816@infradead.org>
On 06/05/2014 01:50 PM, Christoph Hellwig wrote:
> I've been looking into support blk-mq/scsi-mq in dm-mpath, but I'm
> already running into issues with mainline. I created a couple luns
> (without second path) using iet, and then using the iscsi initiator
> to access them. But it seems like no I/O is possible through dm-mpath
> for this simple setup as the kpartx processes spawned by udev already
> hang. Is dm-mpath (default config, no multipath.conf) support to work
> for a single path setup, or is this expected behavior?
>
On a complete different footing, I've whipped together some patches
to simplify the request/bio cloning when using multipath;
basically do _not_ clone the bios, but just modify the rq_end_io
handler.
You mentioned something at LSF that the current way of handling is
quite insane, and looking at it I tend to agree.
So if you'd be interested I'll be posting them.
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-06-05 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 11:50 good dm-mpath test setup? Christoph Hellwig
2014-06-05 12:14 ` Hannes Reinecke
2014-06-05 14:49 ` Christoph Hellwig
2014-06-05 12:17 ` Hannes Reinecke [this message]
2014-06-05 12:20 ` Christoph Hellwig
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=53905FC6.5030006@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.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.