mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jianping Li <jianping.li@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
Subject: Re: [PATCH] arm64: dts: qcom: kodiak: increase fastrpc compute-cb session slots
Date: Thu, 2 Apr 2026 17:48:15 +0800	[thread overview]
Message-ID: <5affb7f3-30c4-4e98-9905-c09154711542@oss.qualcomm.com> (raw)
In-Reply-To: <7b271810-c1ab-4d07-8364-e4c30588722d@oss.qualcomm.com>


On 4/1/2026 7:40 PM, Konrad Dybcio wrote:
> On 4/1/26 1:33 PM, Dmitry Baryshkov wrote:
>> On Wed, Apr 01, 2026 at 03:33:45PM +0800, Jianping Li wrote:
>>> Some workloads on Kodiak can exhaust FastRPC sessions when multiple
>>> compute clients open contexts concurrently, leading to -EBUSY failures.
>>>
>>> Describe the compute context bank with qcom,nsessions = <5> so the
>>> driver can provision enough session slots for the compute-cb instance.
>> This is a software property, so it probably should not have been added
>> to the DT in the first place. Can we replace it with the driver code,
>> allocating more sessions to the last CB?
> Nov 2025 => https://lore.kernel.org/linux-arm-msm/53644b36-2eff-4b1c-9886-591afee8b589@oss.qualcomm.com/
>
> Konrad

Received the comments you gave eariler, currentl checking them.

Thanks,
Jianping.


  reply	other threads:[~2026-04-02  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01  7:33 Jianping Li
2026-04-01 11:33 ` Dmitry Baryshkov
2026-04-01 11:40   ` Konrad Dybcio
2026-04-02  9:48     ` Jianping Li [this message]
2026-04-02  9:41   ` Jianping Li

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=5affb7f3-30c4-4e98-9905-c09154711542@oss.qualcomm.com \
    --to=jianping.li@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=ekansh.gupta@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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®