Thread (18 messages) 18 messages, 4 authors, 2018-01-08

Re: [for-4.16 PATCH v2 1/5] block: establish request failover callback

From: Christoph Hellwig <hch@lst.de>
Date: 2018-01-04 10:28:44
Also in: dm-devel, linux-nvme

On Fri, Dec 29, 2017 at 03:19:04PM -0500, Mike Snitzer wrote:
On Fri, Dec 29 2017 at  5:10am -0500,
Christoph Hellwig [off-list ref] wrote:
quoted
On Tue, Dec 26, 2017 at 10:22:53PM -0500, Mike Snitzer wrote:
quoted
All requests allocated from a request_queue with this callback set can
failover their requests during completion.

This callback is expected to use the blk_steal_bios() interface to
transfer a request's bios back to an upper-layer bio-based
request_queue.

This will be used by both NVMe multipath and DM multipath.  Without it
DM multipath cannot get access to NVMe-specific error handling that NVMe
core provides in nvme_complete_rq().
And the whole point is that it should not get any such access.
No the whole point is you hijacked multipathing for little to no gain.
That is your idea.  In the end there have been a lot of complains about
dm-multipath, and there was a lot of discussion how to do things better,
with a broad agreement on this approach.  Up to the point where Hannes
has started considering doing something similar for scsi.

And to be honest if this is the tone you'd like to set for technical
discussions I'm not really interested.  Please calm down and stick
to a technical discussion.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help