From: Vincent Jardin <vjardin@free.fr>
To: Sahil Malhotra <sahil.malhotra@oss.nxp.com>
Cc: horia.geanta@nxp.com, pankaj.gupta@nxp.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] crypto: caam - never share the gcm and skcipher descriptors serially
Date: Fri, 13 Nov 2026 01:23:34 +0100 [thread overview]
Message-ID: <avZYhjJsa6Ih7nBG@L30177.local> (raw)
In-Reply-To: <20261112101440.673231-1-sahil.malhotra@oss.nxp.com>
Hi Sahil,
> So this needs to be tested on other platforms before it can go in.
> If you have numbers on other SoCs with fewer DECOs, that would be
> helpful. We can also run it on i.MX boards on our side, if you don't
> have access to other boards.
No, I do not have other CPUs than the LX2160 : your feedbacks with i.MX
is welcomed.
> If the regression shows up, one option is to pick the share mode at
> probe time from CHA_NUM_MS[DECO_NUM]: NEVER only when there is more than
> one DECO, SERIAL otherwise.
...
> Do you have similar numbers for authenc and xts, since they use the
> same kind of descriptors?
Since SERIAL vs NEVER impacts the performance depending on the CPU and
on the selected crypto algorithm as you suggest, the code should be more
dynamic, instead of a single option that slows down all the other cases.
How could we keep "selecting" the best one for each case ?
Best regards,
Vincent
prev parent reply other threads:[~2026-11-13 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 23:42 Vincent Jardin via B4 Relay
2026-11-12 10:14 ` Sahil Malhotra
2026-11-13 0:23 ` Vincent Jardin [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=avZYhjJsa6Ih7nBG@L30177.local \
--to=vjardin@free.fr \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=sahil.malhotra@oss.nxp.com \
/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®