mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hanabishi <i.r.e.c.c.a.k.u.n+kernel.org@gmail.com>
To: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>,
	gautham.shenoy@amd.com, mario.limonciello@amd.com,
	perry.yuan@amd.com, rafael@kernel.org, viresh.kumar@linaro.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] cpufreq/amd-pstate: Set initial min_freq to lowest_nonlinear_freq
Date: Sun, 8 Dec 2024 07:54:38 +0000	[thread overview]
Message-ID: <d89bfc1b-37cb-4d8b-b944-8dc385915bcf@gmail.com> (raw)
In-Reply-To: <20241017053927.25285-1-Dhananjay.Ugwekar@amd.com>

Hello. Maybe I'm too late on this, but I have some concerns.

On 10/17/24 05:39, Dhananjay Ugwekar wrote:
> In other systems, power consumption has increased but so has the
> throughput/watt.

I just want to bring up the fact that this change affects all governors. It sounds good for the performance governor, but not so much for the powersave governor.

So the question is: don't we want the lowest power consumption possible in the powersave mode? Even if it means decreased efficiency. Powersave by definition supposed to make battery last as long as possible no matter what, isn't it?


  parent reply	other threads:[~2024-12-08  7:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  5:39 Dhananjay Ugwekar
2024-10-17  5:39 ` [PATCH v3 1/2] cpufreq/amd-pstate: Remove the redundant verify() function Dhananjay Ugwekar
2024-10-17  5:39 ` [PATCH v3 2/2] cpufreq/amd-pstate: Set the initial min_freq to lowest_nonlinear_freq Dhananjay Ugwekar
2024-10-17 14:46   ` Mario Limonciello
2024-12-08  7:54 ` Hanabishi [this message]
2024-12-08 16:35   ` [PATCH v3 0/2] cpufreq/amd-pstate: Set " Mario Limonciello
2025-01-05  3:37     ` Russell Haley
2025-01-06  4:43       ` Dhananjay Ugwekar

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=d89bfc1b-37cb-4d8b-b944-8dc385915bcf@gmail.com \
    --to=i.r.e.c.c.a.k.u.n+kernel.org@gmail.com \
    --cc=Dhananjay.Ugwekar@amd.com \
    --cc=gautham.shenoy@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=perry.yuan@amd.com \
    --cc=rafael@kernel.org \
    --cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®