public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Guixin Liu <kanie@linux.alibaba.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	Keith Busch <kbusch@kernel.org>,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet: handle rw's limited retry flag
Date: Mon, 25 Nov 2024 14:53:37 +0800	[thread overview]
Message-ID: <a336007f-88c1-41e3-826b-e080a4d78213@linux.alibaba.com> (raw)
In-Reply-To: <20241122120959.GA25831@lst.de>


在 2024/11/22 20:09, Christoph Hellwig 写道:
> On Thu, Nov 21, 2024 at 06:24:54PM +0800, Guixin Liu wrote:
>> When the nvme target receive an rw command with limited retry flag,
>> handle it in block backend by setting the REQ_FAILFAST_DEV flag to
>> bio.
> Do you have a use case where this makes a difference?
>
> The code itself looks fine, but I doubt it's actually useful.

In our scenario, our multipath setup places the REQ_FAILFAST_DEV flag on 
I/O to prevent

retries and immediately switch to other paths for issuing I/O commands. 
This will reflect

on the NVMe read and write commands with the limited retry flag. 
However, the current

NVMe target side does not handle the limited retry flag, and the 
target's underlying

driver still retries the I/O. I believe this will result in the I/O not 
being quickly

switched to other paths, ultimately leading to increased I/O latency.

Best Regards,

Guixin Liu



  reply	other threads:[~2024-11-25  6:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 10:24 [PATCH] nvmet: handle rw's limited retry flag Guixin Liu
2024-11-22  6:23 ` Chaitanya Kulkarni
2024-11-22 12:09 ` Christoph Hellwig
2024-11-25  6:53   ` Guixin Liu [this message]
2024-11-25  6:56     ` Christoph Hellwig
2024-11-25  6:57       ` Guixin Liu

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=a336007f-88c1-41e3-826b-e080a4d78213@linux.alibaba.com \
    --to=kanie@linux.alibaba.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.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