Message ID | 20240627083756.25340-1-quic_rampraka@quicinc.com (mailing list archive) |
---|---|
Headers | show |
Series | Suspend clk scaling when there is no request | expand |
On 6/27/24 1:37 AM, Ram Prakash Gupta wrote: > Changes since V1: > - Address minor review comment. This is too vague. Please be more specific in patch changelogs. Thanks, Bart.
On 6/27/2024 10:06 PM, Bart Van Assche wrote: > On 6/27/24 1:37 AM, Ram Prakash Gupta wrote: >> Changes since V1: >> - Address minor review comment. > > This is too vague. Please be more specific in patch changelogs. > > Thanks, > > Bart. > My Bad - will update it properly if next patchset is required. By the way here I addressed code review comment from Dmitry. https://www.spinics.net/lists/kernel/msg5268621.html Thanks, Ram
On 6/27/24 1:37 AM, Ram Prakash Gupta wrote: > Currently ufs clk scaling is getting suspended only when the > clks are scaled down, but next when high load is generated its > adding a huge amount of latency in scaling up the clk and complete > the request post that. > > Now if the scaling is suspended in its existing state, and when high > load is generated it is helping improve the random performance KPI by > 28%. So suspending the scaling when there is no request. And the clk > would be put in low scaled state when the actual request load is low. > > Making this change as optional for other vendor by having the check > enabled using vops as for some vendor suspending without bringing the > clk in low scaled state might have impact on power consumption on the > SoC. For both patches: Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Ram, > Currently ufs clk scaling is getting suspended only when the clks are > scaled down, but next when high load is generated its adding a huge > amount of latency in scaling up the clk and complete the request post > that. Applied to 6.11/scsi-staging, thanks!
On Thu, 27 Jun 2024 14:07:54 +0530, Ram Prakash Gupta wrote: > Currently ufs clk scaling is getting suspended only when the > clks are scaled down, but next when high load is generated its > adding a huge amount of latency in scaling up the clk and complete > the request post that. > > Now if the scaling is suspended in its existing state, and when high > load is generated it is helping improve the random performance KPI by > 28%. So suspending the scaling when there is no request. And the clk > would be put in low scaled state when the actual request load is low. > > [...] Applied to 6.11/scsi-queue, thanks! [1/2] scsi: ufs: Suspend clk scaling on no request https://git.kernel.org/mkp/scsi/c/50183ac2cfb5 [2/2] scsi: ufs: qcom: Enable suspending clk scaling on no request https://git.kernel.org/mkp/scsi/c/ed7dac86f140