From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Uday Shankar <ushankar@purestorage.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>, Jens Axboe <axboe@fb.com>,
Guixin Liu <kanie@linux.alibaba.com>
Subject: Re: [PATCH v3] nvme: avoid fallback to sequential scan due to transient issues
Date: Tue, 15 Nov 2022 00:46:03 +0000 [thread overview]
Message-ID: <4341ec12-338c-3cd6-42f5-db1b66c974b4@nvidia.com> (raw)
In-Reply-To: <20221115002357.3949804-1-ushankar@purestorage.com>
> nvme_scan_ns_sequential(ctrl);
> + } else {
> + ret = nvme_scan_ns_list(ctrl);
> + // fallback to sequential scan if DNR is set to handle broken devices
> + // which should support Identify NS List (as per the VS they report)
> + // but don't actually support it
/**/ comment style plz ..
-ck
next prev parent reply other threads:[~2022-11-15 0:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 0:23 [PATCH v3] nvme: avoid fallback to sequential scan due to transient issues Uday Shankar
2022-11-15 0:46 ` Chaitanya Kulkarni [this message]
2022-11-15 10:18 ` Christoph Hellwig
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=4341ec12-338c-3cd6-42f5-db1b66c974b4@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=ushankar@purestorage.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