From: Keith Busch <kbusch@kernel.org>
To: Mario.Limonciello@dell.com
Cc: hch@lst.de, keith.busch@intel.com, sagi@grimberg.me,
linux-nvme@lists.infradead.org, rafael@kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
kai.heng.feng@canonical.com
Subject: Re: [PATCH] nvme/pci: Use host managed power state for suspend
Date: Mon, 13 May 2019 08:55:24 -0600 [thread overview]
Message-ID: <20190513145522.GA15421@localhost.localdomain> (raw)
In-Reply-To: <b12ff66f8c224e4199ff1b90ed6bc393@AUSX13MPC105.AMER.DELL.COM>
On Mon, May 13, 2019 at 02:43:43PM +0000, Mario.Limonciello@dell.com wrote:
> > Well, it sounds like your partners device does not work properly in this
> > case. There is nothing in the NVMe spec that says queues should be
> > torn down for deep power states, and that whole idea seems rather
> > counter productive to low-latency suspend/resume cycles.
>
> Well I've got a thought, quoting the NVME spec:
> "After a successful completion of a Set Features command for this feature, the controller shall be in the
> Power State specified. If enabled, autonomous power state transitions continue to occur from the new state."
>
> If APST is enabled on this disk, what is to stop an autonomous reverse
> transition from queue activity on the way down?
Regardless of whether APST is enabled or not, the controller may
autonomously transition out of a host requested low power state in
response to host activity. Exiting a low power state should mean some
other task is actively using the device, and if that's the case, why are
you trying to enter a low power state in the first place? Alternatively,
if host activity really is idle, then why is the device autonomously
leaving the requested state?
next prev parent reply other threads:[~2019-05-13 15:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 21:29 [PATCH] nvme/pci: Use host managed power state for suspend Keith Busch
2019-05-11 0:52 ` Mario.Limonciello
2019-05-13 14:24 ` Mario.Limonciello
2019-05-13 14:37 ` Christoph Hellwig
2019-05-13 14:43 ` Mario.Limonciello
2019-05-13 14:54 ` Christoph Hellwig
2019-05-13 14:55 ` Keith Busch [this message]
2019-05-13 15:05 ` Mario.Limonciello
2019-05-13 15:04 ` Keith Busch
2019-05-14 8:04 ` Rafael J. Wysocki
2019-05-14 22:16 ` Keith Busch
2019-05-15 9:00 ` Rafael J. Wysocki
2019-05-13 14:37 ` Keith Busch
2019-05-13 14:54 ` Mario.Limonciello
2019-05-13 14:57 ` Christoph Hellwig
2019-05-13 15:16 ` Keith Busch
2019-05-13 17:16 ` Kai-Heng Feng
2019-05-13 18:16 ` Keith Busch
2019-05-13 18:01 ` Mario.Limonciello
2019-05-14 6:11 ` Christoph Hellwig
2019-05-11 1:33 ` Edmund Nadolski
2019-05-11 7:22 ` Christoph Hellwig
2019-05-12 14:34 ` Sagi Grimberg
2019-05-13 13:36 ` Keith Busch
2019-05-12 6:06 ` Chaitanya Kulkarni
2019-05-12 14:30 ` Minwoo Im
2019-05-12 15:20 ` Chaitanya Kulkarni
2019-05-13 13:47 ` Keith Busch
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=20190513145522.GA15421@localhost.localdomain \
--to=kbusch@kernel.org \
--cc=Mario.Limonciello@dell.com \
--cc=hch@lst.de \
--cc=kai.heng.feng@canonical.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.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