Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: Keith Busch <kbusch@meta.com>,
	hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org
Cc: jmeneghi@redhat.com, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] nvme-multipath: fix io accounting on failover
Date: Wed, 22 May 2024 18:32:11 +0530	[thread overview]
Message-ID: <6e01032f-c90e-4f7e-9339-d2782fd60e3f@linux.ibm.com> (raw)
In-Reply-To: <20240521180712.2423165-1-kbusch@meta.com>



On 5/21/24 23:37, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
> 
> There are io stats accounting that needs to be handled, so don't call
> blk_mq_end_request() directly. Use the existing nvme_end_req() helper
> that already handles everything.
> 
The changes look good however I have a question about why do we retry an IO
when that IO is cancelled? For instance, when a multipath IO request is cancelled 
(from nvme_cancel_request()) we re-queue the bio in nvme_failover_req().
Similarly, for non-multipath request, we do retry request in nvme_retry_req()
until retries for a request are maxed out by nvme_max_retries. So wouldn't it be 
appropriate to drop the cancelled request instead of retrying? 

However, I do understand retrying a request on a different path when we got the 
request completion status specifying the path related error.

Thanks,
--Nilay



  parent reply	other threads:[~2024-05-22 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 18:07 [PATCH] nvme-multipath: fix io accounting on failover Keith Busch
2024-05-21 18:35 ` John Meneghini
2024-05-21 18:55   ` Keith Busch
2024-05-21 19:37 ` Christoph Hellwig
2024-05-21 20:10 ` Sagi Grimberg
2024-05-22 13:02 ` Nilay Shroff [this message]
2024-05-22 14:18   ` Keith Busch
2024-05-23  7:00     ` Nilay Shroff

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=6e01032f-c90e-4f7e-9339-d2782fd60e3f@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=jmeneghi@redhat.com \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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