From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jens Axboe <axboe@fb.com>,
dm-devel@redhat.com, Mike Snitzer <snitzer@redhat.com>
Subject: Re: [PATCH v2] block, dm: don't copy bios for request clones
Date: Sat, 25 Apr 2015 20:13:28 +0200 [thread overview]
Message-ID: <553BD948.5040302@suse.de> (raw)
In-Reply-To: <1429957432-20672-1-git-send-email-hch@lst.de>
On 04/25/2015 12:23 PM, Christoph Hellwig wrote:
> Currently dm-multipath has to clone the bios for every request sent
> to the lower devices, which wastes cpu cycles and ties down memory.
>
> This patch instead adds a new REQ_CLONE flag that instructs req_bio_endio
> to not complete bios attached to a request, which we set on clone
> requests similar to bios in a flush sequence. With this change I/O
> errors on a path failure only get propagated to dm-multipath, which
> can then either resubmit the I/O or complete the bios on the original
> request.
>
Hehe.
I seem to remember having sent a similar patch about a year ago;
which then got shot down due to the missing partial completion
handling.
> I've done some basic testing of this on a Linux target with ALUA support,
> and it survives path failures during I/O nicely.
>
So did I ...
Anyway; we've discussed this at LSF in Boston, haven't we?
AFAICR we've found that having to resubmit the entire command
in the case of partial completion is okay with the storage
vendors, so this patch is a viable way of handling things.
_But_ I really would like to have a consensus here that this
_is_ the correct way of handling partial request; because
if that is the case then we should adopt this strategy
throughout the SCSI layer (ie in scsi_io_completion())
and document the fact.
I really don't like to have two different completion paths;
we should decide on one way and then use it throughout
the stack.
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:[~2015-04-25 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 10:23 [PATCH v2] block, dm: don't copy bios for request clones Christoph Hellwig
2015-04-25 18:13 ` Hannes Reinecke [this message]
2015-04-26 13:35 ` Mike Snitzer
2015-04-26 14:20 ` Christoph Hellwig
2015-04-28 0:59 ` [PATCH v3] " Mike Snitzer
2015-04-28 1:03 ` [PATCH 2/1] dm: do not allocate any mempools for blk-mq request-based DM Mike Snitzer
2015-04-28 6:28 ` Christoph Hellwig
2015-04-28 10:22 ` Mike Snitzer
2015-04-28 5:49 ` [PATCH v3] block, dm: don't copy bios for request clones Hannes Reinecke
2015-04-28 6:29 ` Christoph Hellwig
2015-04-28 9:45 ` Mike Snitzer
2015-05-11 15:55 ` Mike Snitzer
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=553BD948.5040302@suse.de \
--to=hare@suse.de \
--cc=axboe@fb.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.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.