From: Paul Barker <paul.barker.ct@bp.renesas.com>
To: gregkh@linuxfoundation.org
Cc: sudeep.holla@arm.com, rafael@kernel.org, vschneid@redhat.com,
bristot@redhat.com, mgorman@suse.de, bsegall@google.com,
rostedt@goodmis.org, dietmar.eggemann@arm.com,
juri.lelli@redhat.com, peterz@infradead.org, mingo@redhat.com,
lukasz.luba@arm.com, ionela.voinescu@arm.com,
linux-kernel@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [Resend PATCH] topology: Set capacity_freq_ref in all cases
Date: Tue, 13 Feb 2024 11:06:48 +0000 [thread overview]
Message-ID: <8108129e-d7b8-4540-bf53-ed29cd4bbff9@bp.renesas.com> (raw)
In-Reply-To: <75f0bfc7-fb95-409a-a5d9-b00732e892f0@bp.renesas.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1830 bytes --]
Hi Greg,
On 23/01/2024 16:23, Paul Barker wrote:
> On 17/01/2024 19:05, Vincent Guittot wrote:
>> If "capacity-dmips-mhz" is not set, raw_capacity is null and we skip the
>> normalization step which includes setting per_cpu capacity_freq_ref.
>> Always register the notifier but skip the capacity normalization if
>> raw_capacity is null.
>>
>> Fixes: 9942cb22ea45 ("sched/topology: Add a new arch_scale_freq_ref() method")
>> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
>
> We've had some Ethernet performance issues with linux-next and v6.8-rc1
> on the Renesas RZ/G2L and RZ/G2UL arm64 SoCs. I've confirmed that the
> CPU frequency is stuck at the minimum (150MHz) in v6.8-rc1, even when
> running iperf3. Applying this patch allows the SoC to switch up the the
> maximum frequency (1200MHz) when needed and fixes our Ethernet
> performance.
>
> iperf3 results in Mbps for RZ/G2L SMARC evaluation board:
> TCP TX TCP RX UDP TX UDP RX
> v6.8-rc1 255 175 102 (*)
> +this patch 874 650 802 948
>
> (*) Testing UDP RX in v6.8-rc1 with a server sending traffic at 1Gbps
> locks up our NFS rootfs mount so we don't get any result at all.
>
> Results with v6.8-rc1 + this patch are in line with what we see in v6.7.
>
> Tested-by: Paul Barker <paul.barker.ct@bp.renesas.com>
I see this patch landed in the 'driver-core-linus' branch of
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
on 2024-01-30 as commit 98323e9d7017, however it looks like that hasn't
been merged to Linus' tree yet. In v6.8-rc4 I see the same issue on the
RZ/G2L with the CPU frequency stuck at 150MHz.
Is there anything I need to do to help get this patch merged before v6.8
is released?
Thanks,
Paul
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3577 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2024-02-13 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 19:05 Vincent Guittot
2024-01-18 9:42 ` Sudeep Holla
2024-01-18 12:10 ` Dietmar Eggemann
2024-01-18 17:36 ` Pierre Gondois
2024-01-23 15:14 ` Mark Brown
2024-01-23 16:23 ` Paul Barker
2024-02-13 11:06 ` Paul Barker [this message]
2024-02-13 11:45 ` Greg KH
2024-01-31 13:56 ` Erico Nunes
2024-01-31 14:55 ` Vincent Guittot
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=8108129e-d7b8-4540-bf53-ed29cd4bbff9@bp.renesas.com \
--to=paul.barker.ct@bp.renesas.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=ionela.voinescu@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®