The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: llcc: Update the SCT table for IPQ5424
Date: Fri, 7 Aug 2026 17:14:08 +0530	[thread overview]
Message-ID: <c4a85f53-e84f-451e-93fb-e53335e02d17@oss.qualcomm.com> (raw)
In-Reply-To: <q5b6lkfejj6ejqhl7ta7xtmwk4qetnelyxuy6li62vccko27gc@ys5wru2sja2u>


On 8/7/2026 2:35 PM, Dmitry Baryshkov wrote:
> On Fri, Aug 07, 2026 at 02:08:16PM +0530, Kathiravan Thirumoorthy wrote:
>> Update the IPQ5424 LLCC slice configuration table to match the intended
>> cache consumers on the SoC.
>>
>> Assign slice IDs 1 and 5 to the PPE RX descriptor and RX fill use cases,
>> slice IDs 6 and 7 to the Wi-Fi radios connected over PCIe, and slice ID
>> 2 to the CPU subsystem. Adjust the corresponding capacities, priorities,
>> and way masks for these consumers.
>>
>> Rename the usecase IDs for slice IDs 1 and 2 because LLCC_CPUSS and
>> LLCC_VIDSC0 do not describe the actual users of those slices.
> All of this: why? Your tool has provided a summary of the changes, which
> is useless.

Having the dedicated slice configuration for each of these use cases 
helps to improve the networking throughput by more than 1 Gbps.

Let me amend the commit message with the above information. Please let 
me know if that helps.

>
>> Assisted-by: LLM
> Which one?

As per the updated guideline [1], this is what expected.

[1] 816d9992d9ed ("coding-assistants: simplify attribution")

>
>> Signed-off-by: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
>> ---
>>   drivers/soc/qcom/llcc-qcom.c       | 56 ++++++++++++++++++++++++++++++++------
>>   include/linux/soc/qcom/llcc-qcom.h |  4 +++
>>   2 files changed, 52 insertions(+), 8 deletions(-)

      reply	other threads:[~2026-08-07 11:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  8:38 [PATCH] soc: qcom: llcc: Update the SCT table for IPQ5424 Kathiravan Thirumoorthy
2026-08-07  9:05 ` Dmitry Baryshkov
2026-08-07 11:44   ` Kathiravan Thirumoorthy [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=c4a85f53-e84f-451e-93fb-e53335e02d17@oss.qualcomm.com \
    --to=kathiravan.thirumoorthy@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox