Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tokunori Ikegami <ikegami.t@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-nvme@lists.infradead.org, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] nvme: hwmon: Add support for throttling temperature feature
Date: Mon, 8 Aug 2022 00:06:17 +0900	[thread overview]
Message-ID: <a5b9f6a1-1884-0b38-adef-ed47abaf7091@gmail.com> (raw)
In-Reply-To: <20220807060530.GA4018377@roeck-us.net>


On 2022/08/07 15:05, Guenter Roeck wrote:
> On Sat, Aug 06, 2022 at 08:58:49PM +0900, Tokunori Ikegami wrote:
>> Note: Sorry let me resend the mail below as text format since it was not
>> delivered to the mailing lists as contained HTML subpart.
>>
>> Hi,
>>
>> Thanks for your comments.
>>
>> On 2022/08/06 17:31, Guenter Roeck wrote:
>>> On Sat, Aug 06, 2022 at 02:46:06PM +0900, Tokunori Ikegami wrote:
>>>> NVMe drives support host controlled thermal management feature as optional.
>>>> The thermal management temperature are different from the temperature threshold.
>>>> So add functionality to set the throttling temperature values.
>>>>
>>>> Signed-off-by: Tokunori Ikegami <ikegami.t@gmail.com>
>> I think actually the suggested attributes are not met with the throttling
>> temperatures as below.
>>
>>    temp[1-*]_emergency: Temperature emergency max value, for chips supporting
>> more than two upper temperature limits.
>>    temp[1-*]_lcrit: Temperature critical min value, typically lower than
>> corresponding temp_min values.
>>
>>    Thermal Management Temperature 1 (TMT1): This field specifies the
>> temperature, in Kelvins, when the controller begins to transition to lower
>> power active power states or performs vendor specific thermal management
>> actions while minimizing the impact on performance (e.g., light throttling)
>> in order to attempt to reduce the Composite Temperature.
>>    Thermal Management Temperature 2 (TMT2): This field specifies the
>> temperature, in Kelvins, when the controller begins to transition to lower
>> power active power states or perform vendor specific thermal management
>> actions regardless of the impact on performance (e.g., heavy throttling) in
>> order to attempt to reduce the Composite Temperature.
>>
> That happens a lot. That is neither a reason nor an argument to introducing
> new attributes to match chip descriptions. If we would do that, we would end
> up with lots and lots of different and unmanageable attributes.
>
> Please note that the functionality is associated with thermal management,
> so you might want to discuss your attributes with the thermal subsystem
> maintainers.

Okay I see and have understood as it is difficult to use hwmon 
attributes for the thermal management functionality.

Regards,
Ikegami

>
> Guenter


      reply	other threads:[~2022-08-07 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06  5:46 [PATCH] nvme: hwmon: Add support for throttling temperature feature Tokunori Ikegami
2022-08-06  8:31 ` Guenter Roeck
2022-08-06 11:58   ` Tokunori Ikegami
2022-08-06 20:19     ` Armin Wolf
2022-08-07 15:02       ` Tokunori Ikegami
2022-08-07  6:05     ` Guenter Roeck
2022-08-07 15:06       ` Tokunori Ikegami [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=a5b9f6a1-1884-0b38-adef-ed47abaf7091@gmail.com \
    --to=ikegami.t@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux@roeck-us.net \
    /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