Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: NVMe APST high latency power states being skipped
Date: Tue, 23 May 2017 02:42:55 -0700	[thread overview]
Message-ID: <20170523094255.GA12958@infradead.org> (raw)
In-Reply-To: <CAAd53p6uX1pKGAaNhYfT0VSRYD8A2e2Ykacak-pqW4GOXFJPug@mail.gmail.com>

On Tue, May 23, 2017@04:06:27PM +0800, Kai-Heng Feng wrote:
> I have no idea about the performance impact though. Is there any
> benchmark test storage power management latency?

Mostly I want to verify this using some normal workloads - e.g. kernel
compiles are always the kernel hackers favourite, and some application
runs that are easily verifyable, e.g. video playback might be an
interesting one.

  reply	other threads:[~2017-05-23  9:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22  9:04 NVMe APST high latency power states being skipped Kai-Heng Feng
2017-05-23  7:17 ` Christoph Hellwig
2017-05-23  8:06   ` Kai-Heng Feng
2017-05-23  9:42     ` Christoph Hellwig [this message]
2017-05-23 19:35     ` Andy Lutomirski
2017-05-23 19:56       ` Mario.Limonciello
2017-05-23 20:01         ` Andy Lutomirski
2017-05-23 20:19           ` Mario.Limonciello
2017-05-23 21:11             ` Andy Lutomirski
2017-05-23 22:09               ` Mario.Limonciello
2017-05-24  4:53                 ` Kai-Heng Feng
2017-05-24  5:31                   ` Andy Lutomirski
2017-05-25  8:21                     ` Kai-Heng Feng
2017-05-26  9:25                       ` Christoph Hellwig
2017-06-01  8:19                         ` Kai-Heng Feng
2017-06-01 11:32                           ` Christoph Hellwig
2017-06-02  7:08                             ` Kai-Heng Feng
2017-06-02  7:13                               ` Christoph Hellwig
2017-06-06  9:54                                 ` Christoph Hellwig
2017-06-06 15:57                                   ` Andy Lutomirski
2017-06-07  6:19                                     ` Kai-Heng Feng

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=20170523094255.GA12958@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox