feat(crypto): Add crypto perf table for different hardware#652
Draft
jsuhaas22 wants to merge 1 commit intoTexasInstruments:masterfrom
Draft
feat(crypto): Add crypto perf table for different hardware#652jsuhaas22 wants to merge 1 commit intoTexasInstruments:masterfrom
jsuhaas22 wants to merge 1 commit intoTexasInstruments:masterfrom
Conversation
jsuhaas22
requested review from
StaticRocket,
VeeruPrudhvi,
cshilwant,
gehariprasath,
jeevantelukula,
praneethbajjuri and
uditkumarti
as code owners
github-actions
bot
assigned
bryanbrattlof,
devarsht,
DhruvaG2000,
gehariprasath,
jeevantelukula,
praneethbajjuri,
r-vignesh,
sskartheekadivi and
uditkumarti
|
New issues found with check_toc_txt.py: |
|
New warnings found with rstcheck: |
jsuhaas22
force-pushed
the
crypto-perf-compare
branch
from
10b4891 to
5765ba4
Compare
StaticRocket
requested changes
Apr 7, 2026
Comment on lines
+1
to
+12
| .. csv-table:: AES-128-CBC Performance | ||
| :header: "Size (bytes)", "DTHEv2 Accelerator", "ARM CE", "ARM" | ||
| :widths: 30, 30, 30, 30 | ||
|
|
||
| "16", "0.28", "86.86", "28.02" | ||
| "64", "1.16", "271.43", "35.57" | ||
| "256", "4.63", "568.25", "38.33" | ||
| "1024", "17.15", "800.83", "39.08" | ||
| "8192", "82.06", "908.72", "39.31" | ||
| "16384", "112.48", "917.23", "39.02" | ||
| "CPU Usage %", "18", "99", "99" | ||
|
|
Member
There was a problem hiding this comment.
Maybe I'm just a stickler for this, but what unit is that 0.28 and other measurements reported for the given size? I assume it's some unit of time, but it's not particularly clear.
Collaborator
Author
There was a problem hiding this comment.
Its MB/s. I have mentioned it in column headings now.
Comment on lines
+303
to
+322
| ******************************* | ||
| Hardware Performance Comparison | ||
| ******************************* | ||
|
|
||
| The following table shows AES-128-CBC throughput measured using ``openssl speed`` | ||
| across the SA2UL hardware accelerator, ARM Cryptographic Extension (CE), and | ||
| baseline ARM CPU. | ||
|
|
||
| .. ifconfig:: CONFIG_part_variant in ('AM62X') | ||
|
|
||
| .. include:: ../../../../../devices/AM62X/linux/_Crypto_Perf_AES_128_CBC.rst | ||
|
|
||
| .. ifconfig:: CONFIG_part_variant in ('AM62PX') | ||
|
|
||
| .. include:: ../../../../../devices/AM62PX/linux/_Crypto_Perf_AES_128_CBC.rst | ||
|
|
||
| .. ifconfig:: CONFIG_part_variant in ('AM64X') | ||
|
|
||
| .. include:: ../../../../../devices/AM64X/linux/_Crypto_Perf_AES_128_CBC.rst | ||
|
|
Member
There was a problem hiding this comment.
Is there a particular reason this is getting special treatment and not being included in the platform specific performance report that's automatically generated from our test infra?
Collaborator
Author
There was a problem hiding this comment.
We don't have a test ready right now which compares the performance of crypto operations over the 3 hardware options. It's WIP.
Add a performance table which contains the output of `openssl speed ...` command over the 3 different hardware options: SA2UL/DTHEv2 accelerator, ARM CE, and base ARM, for AES-128-CBC algorithm. This gives a clear picture of how crypto operations fare over each IP option. Signed-off-by: Suhaas Joshi <s-joshi@ti.com>
jsuhaas22
force-pushed
the
crypto-perf-compare
branch
from
5765ba4 to
ed36189
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a performance table which contains the output of
openssl speed ...command over the 3 different hardware options: SA2UL/DTHEv2 accelerator, ARM CE, and base ARM, for AES-128-CBC algorithm. This gives a clear picture of how crypto operations fare over each IP option.