From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Giovanni Gherdovich <ggherdovich@suse.cz>,
rafael@kernel.org, lenb@kernel.org, viresh.kumar@linaro.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: intel_pstate: Enable HWP IO boost for all servers
Date: Mon, 20 Mar 2023 11:33:43 -0700 [thread overview]
Message-ID: <cd670ca36053ebf5918a2d1df3255e40edb5f513.camel@linux.intel.com> (raw)
In-Reply-To: <70119ad043502390100e66dbbe658aa069b86e45.camel@suse.cz>
On Mon, 2023-03-20 at 18:03 +0100, Giovanni Gherdovich wrote:
> On Thu, 2023-03-02 at 20:14 -0800, Srinivas Pandruvada wrote:
>
...
Hi Giovanni,
> Hello Srinivas,
>
> Good catch. We've had HWP IO Boost in the kernel for a while now but
> we
> weren't enabling on most of the modern CPUs... This fixes it.
>
> One thing though: I've the impression that HWP IO Boost depends on
> having
> per-core p-states -- otherwise you'll be boosting up and down the
> entire machine
> instead of just the one core waking up from IO.
> Enabling the feature on all machines with the ACPI PM server profile
> would
> force it also where per-core p-states aren't available.
This feature only exists on HWP systems. There are no HWP systems
without per core P-states. Here we are enabling for performance and
enterprise servers only.
>
> Would you agree with this assessment?
> Do I correctly understand the reason why per-core p-states are needed
> here?
This problem with IO will be more pronounced in per-core P-states
systems as it will not be influenced by other cores. But even if non
per-core systems if other cores are idle or lightly loaded, the same
problem can occur. But I don't have data on such systems.
>
> I remember you mentioned the the dependency on per-core p-states in
> the cover
> letter from the HWP IO Boost submission in 2018
> https://lore.kernel.org/lkml/20180605214242.62156-1-srinivas.pandruvada@linux.intel.com/
>
> I think there's a tradeoff here. Up until this patch, we forgot to
> enable the
> feature on four generations of Intel CPUs. That's a lot of lost
> performance;
> thanks to this patch it won't happen ever again, because nobody will
> have to
> update the model list at every new CPU release.
>
CPU model updates always gets missed and also misses testing
opportunity.
> On the other side, there may be some penalty for machines that:
> - have HWP
> - don't have per-core p-states
> I don't know how large that interesection is, or how big the penalty.
>
Thanks,
Srinivas
>
> Giovanni
>
prev parent reply other threads:[~2023-03-20 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 4:14 [PATCH] cpufreq: intel_pstate: Enable HWP IO boost for all servers Srinivas Pandruvada
2023-03-17 17:38 ` Rafael J. Wysocki
2023-03-20 17:03 ` Giovanni Gherdovich
2023-03-20 18:33 ` srinivas pandruvada [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=cd670ca36053ebf5918a2d1df3255e40edb5f513.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=ggherdovich@suse.cz \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).