From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: good dm-mpath test setup?
Date: Thu, 5 Jun 2014 05:20:38 -0700 [thread overview]
Message-ID: <20140605122038.GA13185@infradead.org> (raw)
In-Reply-To: <53905FC6.5030006@suse.de>
On Thu, Jun 05, 2014 at 02:17:10PM +0200, Hannes Reinecke wrote:
> 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.
Please do - that's something mostly orthogonal to my patches, but with
the bio cloning removed and my conversion to blk-mq dm-mpath will become
really lean and simple.
prev parent reply other threads:[~2014-06-05 12:20 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
2014-06-05 12:20 ` Christoph Hellwig [this message]
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=20140605122038.GA13185@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
/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.