From: Herbert Xu <herbert@gondor.apana.org.au>
To: vjardin@free.fr
Cc: "Horia Geantă" <horia.geanta@nxp.com>,
"Pankaj Gupta" <pankaj.gupta@nxp.com>,
"Sahil Malhotra" <sahil.malhotra@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Gaurav Jain" <gaurav.jain@nxp.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] crypto: caam/qi2 - algorithm priority be a parameter
Date: Tue, 29 Sep 2026 22:29:24 +1000 [thread overview]
Message-ID: <aruvJECCDNdguMdw@gondor.apana.org.au> (raw)
In-Reply-To: <20260928-for-upstream-caam-qi2-priority-v1-1-e4a8e5f01dbc@free.fr>
On Mon, Sep 28, 2026 at 04:01:03PM +0200, Vincent Jardin via B4 Relay wrote:
> From: Vincent Jardin <vjardin@free.fr>
>
> dpaa2_caam registers every skcipher, aead and ahash at a fixed priority
> of 2000.
>
> It is above the ARMv8 Crypto Extensions (200 to 300), so on any DPAA2 SoC,
> every in-kernel user of AES, SHA or GCM moves from the CPU to the SEC,
> whatever the request size.
>
> Whether the SEC should be the default or only be reached by driver name
> depends on the system, and there is no way to choose/tune it.
You can easily change the priority from user-space through the
crypto_user interface.
So why not lower the default priority and let the user adjust
it if necessary?
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2026-09-29 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 14:01 [PATCH 0/3] crypto: caam/qi2 - algorithm priority configurable Vincent Jardin via B4 Relay
2026-09-28 14:01 ` [PATCH 1/3] crypto: caam/qi2 - algorithm priority be a parameter Vincent Jardin via B4 Relay
2026-09-29 12:29 ` Herbert Xu [this message]
2026-09-29 12:57 ` Vincent Jardin
2026-09-28 14:01 ` [PATCH 2/3] dt-bindings: crypto: fsl,sec-v4.0: add fsl,qi2-crypto-priority Vincent Jardin via B4 Relay
2026-09-29 9:08 ` Krzysztof Kozlowski
2026-09-29 12:58 ` Vincent Jardin
2026-09-28 14:01 ` [PATCH 3/3] crypto: caam/qi2 - priority from the DTS Vincent Jardin via B4 Relay
2026-09-28 22:41 ` [PATCH 0/3] crypto: caam/qi2 - algorithm priority configurable Eric Biggers
2026-09-29 16:45 ` Vincent Jardin
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=aruvJECCDNdguMdw@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gaurav.jain@nxp.com \
--cc=horia.geanta@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=robh@kernel.org \
--cc=sahil.malhotra@nxp.com \
--cc=vjardin@free.fr \
/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®