public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "sagi@grimberg.me" <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] nvme: add support for TP4084 - Time-to-Ready Enhancements
Date: Wed, 18 May 2022 16:14:37 +0000	[thread overview]
Message-ID: <ba9454ef-20ea-2a8d-558a-e0fef33deaeb@nvidia.com> (raw)
In-Reply-To: <20220518150044.GA1359@lst.de>

On 5/18/22 08:00, Christoph Hellwig wrote:
> On Wed, May 18, 2022 at 08:36:47AM -0600, Keith Busch wrote:
>> On Wed, May 18, 2022 at 08:40:40AM +0200, Christoph Hellwig wrote:
>>> +static int nvme_identify_ns_cs_indep(struct nvme_ctrl *ctrl, unsigned nsid,
>>> +			struct nvme_id_ns_cs_indep **id)
>>> +{
>>> +	struct nvme_command c = {
>>> +		.identify.opcode	= nvme_admin_identify,
>>> +		.identify.nsid		= cpu_to_le32(nsid),
>>> +		.identify.cns		= NVME_ID_CNS_NS_CS_INDEP,
>>> +	};
>>> +	int error;
>>
>> Every other place in this driver calls this value 'ret'.
> 
> Except for nvme_identify_ns, where I copied it from :)
> 
> But I can change it to ret.

that'd be great.

[...]

> 
> ---
>  From 032b8a803bf5bec4c4f206d9cc5a4b1160e0dc69 Mon Sep 17 00:00:00 2001
> From: Christoph Hellwig <hch@lst.de>
> Date: Mon, 16 May 2022 15:09:21 +0200
> Subject: nvme: add support for TP4084 - Time-to-Ready Enhancements
> 
> Add support for using longer timeouts during controller initialization
> and letting the controller come up with namespaces that are not ready
> for I/O yet.  We skip these not ready namespaces during scanning and
> only bring them online once anoter scan is kicked off by the AEN that
> is set when the NRDY bit gets set in the  I/O Command Set Independent
> Identify Namespace Data Structure.   This asynchronous probing avoids
> blocking the kernel boot when controllers take a very long time to
> recover after unclean shutdowns (up to minutes).
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---


Thanks for not adding a new member to nvme_ctrl any new member.
Looks good.

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

-ck



  parent reply	other threads:[~2022-05-18 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18  6:40 [PATCH] nvme: add support for TP4084 - Time-to-Ready Enhancements Christoph Hellwig
2022-05-18  9:26 ` Hannes Reinecke
2022-05-18 14:36 ` Keith Busch
2022-05-18 15:00   ` Christoph Hellwig
2022-05-18 15:09     ` Keith Busch
2022-05-18 16:14     ` Chaitanya Kulkarni [this message]
2022-05-20 11:51     ` Niklas Cassel
2022-05-20 14:13       ` Keith Busch
2022-05-25 16:19         ` Niklas Cassel
2022-05-25 16:23           ` 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=ba9454ef-20ea-2a8d-558a-e0fef33deaeb@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --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