Linux Device Mapper development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>, 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: Sun, 26 Apr 2015 07:20:23 -0700	[thread overview]
Message-ID: <20150426142020.GB7085@infradead.org> (raw)
In-Reply-To: <553BD948.5040302@suse.de>

On Sat, Apr 25, 2015 at 08:13:28PM +0200, Hannes Reinecke wrote:
> I seem to remember having sent a similar patch about a year ago;

This one?
http://www.redhat.com/archives/dm-devel/2014-June/msg00023.html

> which then got shot down due to the missing partial completion
> handling.

It got shot down because it passed the upper level request down,
which is a non-no for blk-mq.

> 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.

Yes.  But even if it wasn't for some reason we could inspect blk_rq_bytes()
on the clone and do a partial completion on the original request, but
I'd prefer to avoid special casing this case if we can avoid it.

> _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.

SCSI is a very different case, we do regularly get patial completions
from arrays, and we need to handle them efficiently in the normal
I/O path.  The only case where we will resubmit completed I/O in
dm-mpath is when we got a successfull partial completion in SCSI,
and then a following completions returns an error that causes a
failover.  I don't think there is a need to micro-optimize this case.

  parent reply	other threads:[~2015-04-26 14:20 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
2015-04-26 13:35   ` Mike Snitzer
2015-04-26 14:20   ` Christoph Hellwig [this message]
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=20150426142020.GB7085@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@fb.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    --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