From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Yaxiong Tian <iambestgod@qq.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>, "hch@lst.de" <hch@lst.de>,
"sagi@grimberg.me" <sagi@grimberg.me>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yaxiong Tian <tianyaxiong@kylinos.cn>
Subject: Re: [PATCH v3 0/3] nvme: Add sysfs interface for APST configuration management
Date: Tue, 1 Apr 2025 22:33:43 +0000 [thread overview]
Message-ID: <525d312b-0a59-4623-8640-e83a1231e100@nvidia.com> (raw)
In-Reply-To: <tencent_4612952C8C5109058CD8E688D81276A2FD0A@qq.com>
On 4/1/25 02:22, Yaxiong Tian wrote:
> From: Yaxiong Tian<tianyaxiong@kylinos.cn>
>
> This series enhances NVMe APST (Autonomous Power State Transition) support by:
> 1. Adding warnings for PST table allocation failures
> 2. Exposing APST tables via sysfs for runtime inspection
> 3. Providing per-controller sysfs interface for APST configuration
>
> The changes allow better visibility and control of power management settings
> through userspace tools while maintaining the existing functionality.
For the series looks good, I believe it is tested with blktest and there are
no issues ...
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2025-04-01 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 9:22 Yaxiong Tian
2025-04-01 9:26 ` [PATCH v3 1/3] nvme: Add warning for PST table memory allocation failure in nvme_configure_apst Yaxiong Tian
2025-04-03 4:25 ` Christoph Hellwig
2025-04-03 7:08 ` Yaxiong Tian
2025-04-01 9:27 ` [PATCH v3 2/3] nvme: add sysfs interface for APST table updates Yaxiong Tian
2025-04-01 9:27 ` [PATCH v3 3/3] nvme: add per-controller sysfs interface for APST configuration Yaxiong Tian
2025-04-01 22:33 ` Chaitanya Kulkarni [this message]
2025-04-03 4:25 ` [PATCH v3 0/3] nvme: Add sysfs interface for APST configuration management Christoph Hellwig
2025-04-03 7:05 ` Yaxiong Tian
2025-04-04 8:29 ` Christoph Hellwig
2025-04-06 9:14 ` Alexey Bogoslavsky
2025-04-07 1:25 ` Yaxiong Tian
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=525d312b-0a59-4623-8640-e83a1231e100@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=iambestgod@qq.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=tianyaxiong@kylinos.cn \
/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®