From: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Thara Gopinath <thara.gopinath@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Bartosz Golaszewski <brgl@kernel.org>,
Gaurav Kashyap <gaurav.kashyap@oss.qualcomm.com>,
Neeraj Soni <neeraj.soni@oss.qualcomm.com>
Subject: Re: [PATCH 0/3] Add support for qcrypto on shikra
Date: Mon, 25 May 2026 11:10:10 +0530 [thread overview]
Message-ID: <c1697372-54ec-4f57-85d9-ad375ff1a44d@oss.qualcomm.com> (raw)
In-Reply-To: <20260522024912.GC5937@quark>
> It sounds like you don't actually have an answer to my questions, then.
>
> Performance tests (e.g.
> https://lore.kernel.org/r/20250615031807.GA81869@sol/) have clearly
> shown that this driver is an order of magnitude slower than the CPU.
>
> This driver has historically been quite harmful. People were using it
> accidentally and encountering very bad performance, as well as bugs such
> as crashes and filesystem hangs. We fixed that by lowering its
> cra_priority. But for the same reason, even when enabled on a platform,
> it's not actually used. Linux would be better without this driver.
>
+Bartosz, Gaurav, Neeraj
Hi Eric,
GPCE is relevant in terms of providing hardware security.
There are multiple usecases coming up for example to handle DRM/secure
buffer usecases to improve overall throughput for secure content.
Regarding performance, it's currently slower compared to arm CE but
provides an edge by giving hardware security which is considered more
secure.
Btw, there's been performance improvement with new targets and we are
expecting to achieve far more better performance with new SoCs family.
Pakala: GPCE - 550MBps, ARMv8 - 8GBps
Kaanapali: GPCE - 3GBps, ARMv8 - 10GBps
Please note, there's almost 5x improvement in kaanapali compared to
pakala. Though overall is still slower compared to arm but as mentioned,
expecting better performance with hardware improvements as we progress.
Also, currently qce driver exhibit stability issues and that's what we
are putting effort in stabilizing the software on immediate basis.
There's parallel effort ongoing by Bartosz to introduce baseline for
secure buffer usecases.
https://lore.kernel.org/lkml/20260522-qcom-qce-cmd-descr-v18-0-99103926bafc@oss.qualcomm.com/
There's active development ongoing and i believe lowering cra_priority
for qce is fine as of now and can scale values once qce becomes
performance efficient.
Please share your thoughts. Thanks!
--
Regards
Kuldeep
next prev parent reply other threads:[~2026-05-25 5:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 19:23 [PATCH 0/3] Add support for qcrypto on shikra Kuldeep Singh
2026-05-14 19:23 ` [PATCH 1/3] dt-bindings: crypto: qcom-qce: Document the Shikra crypto engine Kuldeep Singh
2026-05-15 11:00 ` Krzysztof Kozlowski
2026-05-19 7:09 ` Kuldeep Singh
2026-05-19 7:27 ` Krzysztof Kozlowski
2026-05-19 8:55 ` Kuldeep Singh
2026-05-14 19:23 ` [PATCH 2/3] dt-bindings: bam-dma: Increase maxItems to seven for iommus Kuldeep Singh
2026-05-14 19:23 ` [PATCH 3/3] arm64: dts: qcom: shikra: Add qcrypto node support Kuldeep Singh
2026-05-15 10:28 ` Konrad Dybcio
2026-05-21 8:45 ` Kuldeep Singh
2026-05-25 8:47 ` Dmitry Baryshkov
2026-05-25 10:09 ` Kuldeep Singh
2026-05-25 10:43 ` Dmitry Baryshkov
2026-05-14 19:47 ` [PATCH 0/3] Add support for qcrypto on shikra Eric Biggers
2026-05-21 6:51 ` Kuldeep Singh
2026-05-22 2:49 ` Eric Biggers
2026-05-25 5:40 ` Kuldeep Singh [this message]
2026-05-25 14:28 ` Eric Biggers
2026-05-25 15:26 ` Eric Biggers
2026-05-28 11:54 ` Kuldeep Singh
2026-05-28 13:13 ` Bartosz Golaszewski
2026-05-28 13:50 ` Dmitry Baryshkov
2026-05-28 15:13 ` Bartosz Golaszewski
2026-05-28 17:52 ` Eric Biggers
2026-05-29 15:58 ` Bartosz Golaszewski
2026-06-10 6:05 ` Kuldeep Singh
2026-05-25 10:07 ` Dmitry Baryshkov
2026-05-25 14:45 ` Eric Biggers
2026-06-08 10:35 ` Kuldeep Singh
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=c1697372-54ec-4f57-85d9-ad375ff1a44d@oss.qualcomm.com \
--to=kuldeep.singh@oss.qualcomm.com \
--cc=Frank.Li@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=gaurav.kashyap@oss.qualcomm.com \
--cc=herbert@gondor.apana.org.au \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.soni@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=thara.gopinath@gmail.com \
--cc=vkoul@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