From: Georg Gottleuber <g.gottleuber@tuxedocomputers.com>
To: Christoph Hellwig <hch@lst.de>, Werner Sembach <wse@tuxedocomputers.com>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Sagi Grimberg <sagi@grimberg.me>,
Georg Gottleuber <ggo@tuxedocomputers.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme-pci: Add sleep quirk for Kingston drives
Date: Thu, 7 Dec 2023 15:21:55 +0100 [thread overview]
Message-ID: <c930e543-7dab-4559-95d2-270b8df38f3b@tuxedocomputers.com> (raw)
In-Reply-To: <20231206092420.GA27348@lst.de>
Am 06.12.23 um 10:24 schrieb Christoph Hellwig:
> What does save a lot of power mean, and why does it only apply to
> some platforms? I suspect the more likely case is that APST is
> simply completely broken on this device?
Hello,
power consumption in s0ix varies depending on mainboard and NVMe SSD.
Some examples:
Board, nvme(id), mW w/o patch, mW with patch, kernel
NS5X_SN7XAU, 0x500f, 2691mW, 487mW, 6.2.0
NS5X_SN7XAU, 0x2263, 2262mW, 741mW, 6.2.0
PH4PRX1_PH6PRX1, 0x2263, 3042mW, 760mW, 6.2.0
NS5X_SN7XPU, 0x500f, 3135mW, 779mW, 6.5.0
All measurements were taken with the battery disconnected and a
modified adapter plug.
I don't have a deeper insight into APST to judge whether something is
not working. But all other NVMe SSDs we have tested sleep with a power
consumption below 2W (Samsung 970 Evo, Samsung 980, Corsair MP600 PRO
NH, other Kingston NV1 with ID != 0x500f).
We originally noticed that newer Kingston NV1 (with id 500f) led to
higher standby consumption. With some trial and error I came to the
conclusion that the problem lies with 'Simple Suspend'.
Kind regards,
Georg Gottleuber
next prev parent reply other threads:[~2023-12-07 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 8:52 Werner Sembach
2023-12-05 17:17 ` Werner Sembach
2023-12-06 9:24 ` Christoph Hellwig
2023-12-07 14:21 ` Georg Gottleuber [this message]
2023-12-07 15:20 ` Christoph Hellwig
2023-12-07 17:00 ` 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=c930e543-7dab-4559-95d2-270b8df38f3b@tuxedocomputers.com \
--to=g.gottleuber@tuxedocomputers.com \
--cc=axboe@kernel.dk \
--cc=ggo@tuxedocomputers.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=wse@tuxedocomputers.com \
/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
all inboxes | Powered by JetHome®