All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v2] nvme: Honor RTD3 Entry Latency for shutdowns
Date: Thu, 24 Aug 2017 02:02:22 -0700	[thread overview]
Message-ID: <20170824090222.GA2543@infradead.org> (raw)
In-Reply-To: <20170823223258.6695-1-martin.petersen@oracle.com>

On Wed, Aug 23, 2017@06:32:58PM -0400, Martin K. Petersen wrote:
> If an NVMe v1.2+ compliant controller reports RTD3 Entry Latency larger
> than shutdown_timeout, up to a maximum of 60 seconds, use that value to
> set the shutdown timer. Otherwise fall back to the module parameter
> which defaults to 5 seconds.

This generally looks fine, but NVMe allows TPs and thus new fields
to be implemented even against older spec versions, so we should avoid
version tests wherever possible.

> +	if (ctrl->vs >= NVME_VS(1, 2, 0)) {
> +		u32 transition_time = le32_to_cpu(id->rtd3e);

So instead of the version check here I'd check for a non-zero
RTD3E field instead.

  reply	other threads:[~2017-08-24  9:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 19:55 [PATCH] nvme: Honor RTD3 Entry Latency for shutdowns Martin K. Petersen
2017-08-16 20:25 ` Scott Bauer
2017-08-16 20:49   ` Martin K. Petersen
2017-08-17 15:01     ` Keith Busch
2017-08-17 17:06       ` Martin K. Petersen
2017-08-17 17:42         ` Scott Bauer
2017-08-23 22:32           ` [PATCH v2] " Martin K. Petersen
2017-08-24  9:02             ` Christoph Hellwig [this message]
2017-08-25  2:26               ` Martin K. Petersen
2017-08-25  2:26               ` [PATCH v3] " Martin K. Petersen
2017-08-25  7:41                 ` Christoph Hellwig
2017-08-25 14:15                   ` Martin K. Petersen
2017-08-25 19:56                 ` Keith Busch
2017-08-25 23:14                   ` [PATCH v4] " Martin K. Petersen
2017-08-28  6:05                     ` Sagi Grimberg
2017-08-28 14:22                     ` Keith Busch
2017-08-25 23:16                   ` [PATCH v3] " Martin K. Petersen

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=20170824090222.GA2543@infradead.org \
    --to=hch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.