All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pushpendra Singh <pushpendra.singh@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	andersson@kernel.org, konradybcio@kernel.org,
	abelvesa@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] devfreq: qcom: bwmon: Reduce zone1 threshold count to 3
Date: Fri, 20 Nov 2026 16:31:25 +0530	[thread overview]
Message-ID: <9130f308-e264-4ada-87cc-95553c5e9e0f@oss.qualcomm.com> (raw)
In-Reply-To: <cf2091e5-44a3-473a-a5e4-d9044b053b45@kernel.org>



On 11/19/2026 5:37 PM, Krzysztof Kozlowski wrote:
> On 19/11/2026 12:44, Pushpendra Singh wrote:
>> Reduce zone1_thres_count from 16 to 3 so the driver can lower the bus
>> vote after 3 sample windows instead of waiting for 16. The previous
>> 16‑window delay (~64 ms) is too long at higher FPS workloads,
>> causing delayed decision making and measurable power regression.
>>
>> Power and performance measurements were collected for
>> zone1_thres_count = 3 and 16, with the following results:
>>
>> Usecase                         zone1_cnt=16	zone1_cnt=3       Delta
>> YouTube streaming (power)	4126.49 mW	3991.30 mW      -3.28%
>> Google Meet audio (power)	3058.79 mW	2929.73 mW      -4.22%
>> Speedometer 3.1(perf)		25.8		26.5            +2.7%
>> Geekbench 6.5 ST(perf)		3907		3905            -0.1%
>> Geekbench 6.5 MT(perf)		18636		18680           +0.2%
>>
>> The reduced threshold therefore allows BWMON to react sooner to falling
>> bandwidth demand, providing measurable power savings in the tested
>> workloads without a meaningful performance regression.
> 
> I do not see how you resolved my comment, so same comment.

Thanks for the feedback. I had addressed the previous comment by rerunning the power and performance measurements on the latest kernel (v7.3.rc5) and shared the updated results in my previous reply[1]. I have also included these results in the commit message in this respin.

Could you please clarify if there is any additional concern that I may have missed? I’ll be happy to address it.

[1]
https://lore.kernel.org/lkml/34ada002-5271-4f05-8b6b-ee4294f2ebee@oss.qualcomm.com/

Thanks,
Pushpendra Singh

> 
> Best regards,
> Krzysztof


  reply	other threads:[~2026-11-20 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19 11:44 [PATCH v4] devfreq: qcom: bwmon: Reduce zone1 threshold count to 3 Pushpendra Singh
2026-11-19 12:07 ` Krzysztof Kozlowski
2026-11-20 11:01   ` Pushpendra Singh [this message]
2026-11-20 11:46     ` Krzysztof Kozlowski

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=9130f308-e264-4ada-87cc-95553c5e9e0f@oss.qualcomm.com \
    --to=pushpendra.singh@oss.qualcomm.com \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.