From: Keith Busch <kbusch@kernel.org>
To: "Engel, Amit" <Amit.Engel@Dell.com>
Cc: "Anner, Ran" <Ran.Anner@dell.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: nvme reservation commands during controller reset
Date: Sun, 9 Aug 2020 10:10:16 -0600 [thread overview]
Message-ID: <20200809161016.GA63121@C02WT3WMHTD6> (raw)
In-Reply-To: <MN2PR19MB30052441F4F22A4CAC8D396FEE4B0@MN2PR19MB3005.namprd19.prod.outlook.com>
On Wed, Aug 05, 2020 at 07:14:22AM +0000, Engel, Amit wrote:
> What is the reason for setting REQ_FAILFAST_DRIVER flag in nvme_alloc_request ?
> The original intention was to mark only sync cmds as failfast ?
Special requests don't get generic error handling. The caller gets to decide
how to handle it.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-08-09 16:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 7:14 nvme reservation commands during controller reset Engel, Amit
2020-08-09 16:10 ` Keith Busch [this message]
2020-08-10 12:40 ` Christoph Hellwig
2020-08-10 15:13 ` Engel, Amit
2020-08-10 15:48 ` Keith Busch
2020-08-11 20:48 ` Sagi Grimberg
2020-08-12 7:00 ` Engel, Amit
2020-08-14 8:20 ` Christoph Hellwig
2020-08-14 10:09 ` Christoph Hellwig
2020-08-14 16:02 ` Keith Busch
2020-08-15 7:00 ` Christoph Hellwig
2020-08-14 18:29 ` Sagi Grimberg
2020-08-15 7:01 ` Christoph Hellwig
2020-08-17 7:56 ` Sagi Grimberg
2020-08-17 8:12 ` Christoph Hellwig
2020-08-17 19:29 ` Sagi Grimberg
2020-08-18 6:36 ` Christoph Hellwig
2020-08-18 17:18 ` Sagi Grimberg
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=20200809161016.GA63121@C02WT3WMHTD6 \
--to=kbusch@kernel.org \
--cc=Amit.Engel@Dell.com \
--cc=Ran.Anner@dell.com \
--cc=linux-nvme@lists.infradead.org \
/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