From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Paul Menzel <pmenzel+linux-nvme@molgen.mpg.de>
Cc: Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: Report long suspend times of NVMe devices (mostly firmware/device issues)
Date: Mon, 22 Jan 2018 16:31:11 -0500 [thread overview]
Message-ID: <yq1efmhk2cg.fsf@oracle.com> (raw)
In-Reply-To: <9e398971-762d-bb1a-f798-bf0b18cb5b6b@molgen.mpg.de> (Paul Menzel's message of "Mon, 22 Jan 2018 22:02:12 +0100")
Paul,
> In my opinion anything longer than 200 ms should be reported similar to
> [2], and maybe worded like below.
There are many controllers out there that take double-digit seconds to
shut down.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-01-22 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 21:02 Report long suspend times of NVMe devices (mostly firmware/device issues) Paul Menzel
2018-01-22 21:30 ` Keith Busch
2018-01-24 22:29 ` Paul Menzel
2018-01-24 22:47 ` Keith Busch
2018-01-22 21:31 ` Martin K. Petersen [this message]
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=yq1efmhk2cg.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=pmenzel+linux-nvme@molgen.mpg.de \
--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