From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] soc: qcom: llcc: Update the SCT table for IPQ5424
Date: Wed, 19 Aug 2026 20:24:00 +0530 [thread overview]
Message-ID: <18eb2d9f-474c-4b1c-bb57-87c7568f6612@oss.qualcomm.com> (raw)
In-Reply-To: <28bffcd1-4743-43ae-936b-9f9f92117a9e@oss.qualcomm.com>
On 8/19/2026 5:23 PM, Konrad Dybcio wrote:
> On 8/11/26 2:34 PM, Kathiravan Thirumoorthy wrote:
>> Update the IPQ5424 LLCC slice configuration table to give the PPE
>> and Wi-Fi datapaths dedicated slices.
>>
>> 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.
>>
>> Having the dedicated slice configuration for each of these use cases helps
>> to improve the networking throughput by more than 1 Gbps.
>>
>> 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.
> This reiterates the diff, but doesn't mention the actual reason for this
> change (updated recommendations from the hardware team)
These slice assignments are based on recommendations from our
performance team, following throughput measurements on IPQ5424 — not
from a hardware team. Please let me know if I'm missing something here.
>
> Konrad
next prev parent reply other threads:[~2026-08-19 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 12:34 Kathiravan Thirumoorthy
2026-08-11 13:49 ` Dmitry Baryshkov
2026-08-19 11:53 ` Konrad Dybcio
2026-08-19 14:54 ` Kathiravan Thirumoorthy [this message]
2026-08-19 14:55 ` Konrad Dybcio
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=18eb2d9f-474c-4b1c-bb57-87c7568f6612@oss.qualcomm.com \
--to=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@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
all inboxes | Powered by JetHome®