Skip to content

Commit

Permalink
Some more Phytium and Qualcomm Falkor V1 stuff
Browse files Browse the repository at this point in the history
  • Loading branch information
ThomasKaiser committed Nov 8, 2022
1 parent 2e7e88a commit f27fceb
Show file tree
Hide file tree
Showing 4 changed files with 638 additions and 8 deletions.
16 changes: 9 additions & 7 deletions results/ARMv8-Crypto-Extensions.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

SoC vendors who license ARMv8 cores (usually 64-bit capable) can decide between certain optional features: for example cryptographic acceleration called ['ARMv8 Cryptography Extensions'](https://developer.arm.com/documentation/ddi0500/e/CJHDEBAF).

Usually SoC vendors do, the only known exceptions are early Cortex-A53 SoCs like Qualcomm's Snapdragon 410, Amlogic's very first 64-bit SoC S905 (used only on ODROID-C2 and NanoPi K2) and BroadCom's SoCs powering all 64-bit capable Raspberry Pis: all lack any crypto acceleration and perform way lower than all other 64-bit ARM SoCs in this area.
Usually SoC vendors do, the only known exceptions are early Cortex-A53 SoCs like Qualcomm's Snapdragon 410, Amlogic's very first 64-bit SoC S905 (used only on ODROID-C2 and NanoPi K2), Phytium's FTC662 core and BroadCom's SoCs powering all 64-bit capable Raspberry Pis: all lack any crypto acceleration and perform way lower than all other 64-bit ARM SoCs in this area.

If the kernel has been built correctly, availability of accelerated cryptography functions can be checked by querying `/proc/cpuinfo`: The 'Features' entry will additionally show `aes pmull sha1 sha2`.

Expand All @@ -31,14 +31,14 @@ _ARMv8 Crypto Extensions_ are not a classic 'crypto engine' running at a fixed c

### Scores predictable based on CPU core and clockspeed

It all boils down to type of ARM core and CPU clockspeed since the ratio between openssl score and CPU clockspeed is fixed in the following way (using sbc-bench result collection as base which unfortunately misses all more modern ARM cores than A73 and A76):
It all boils down to type of ARM core and CPU clockspeed since the ratio between openssl score and CPU clockspeed is fixed in the following way (using sbc-bench result collection):

* Cortex-A35: ~217, an A35 running at 1000 MHz will produce an ~217000k aes-256-cbc score (or ~434000k at 2000 MHz)
* Cortex-A57: ~359, an A57 running at 1000 MHz will produce an ~359000k aes-256-cbc score (or ~718000k at 2000 MHz)
* Cortex-A53/A55: ~467, A53/A55 running at 1000 MHz will produce an ~467000k aes-256-cbc score (or ~935000k at 2000 MHz)
* Cortex-A72/A73/A76: ~570, A72/A73/A76 running at 1000 MHz will produce an ~570000k aes-256-cbc score (or ~1140000k at 2000 MHz)
* Cortex-A72/A73/A76/A77/A78: ~570, A72/A73/A76 running at 1000 MHz will produce an ~570000k aes-256-cbc score (or ~1140000k at 2000 MHz)

Amazon's Graviton/Graviton2 ARM CPUs score identical to A72/A73/A76 and the custom FTC663 core inside the [Feiteng D2000 CPU](https://en.wikipedia.org/wiki/FeiTeng_(processor)#Future_processors) performs identical to an A57. NVidia's Carmel core performs marginally better than Cortex-A57 (~374, the Jetson Xavier NX numbers below). Qualcomm's Kryo Silver cores are based on A55 and perform exactly the same here.
Amazon's Graviton/Graviton2 ARM CPUs and Neoverse-N1 cores score identical to A72/A73/A76/A77/A78 and the custom FTC663 core inside the [Feiteng D2000 CPU](https://en.wikipedia.org/wiki/FeiTeng_(processor)#Future_processors) performs identical to an A57 ([another hint wrt similarity](https://github.com/martin-frbg/OpenBLAS/blob/b3b4672c30f613c0043ad0557d33a34ffa3bbd0d/kernel/arm64/KERNEL.FT2000)). NVidia's Carmel core performs marginally better than Cortex-A57 (~374, the Jetson Xavier NX numbers below). Qualcomm's Kryo Silver cores are based on A55 and perform exactly the same here while Qualcomm's Qualcomm Falkor V1 behaves like Cortex-A72 and onwards.

### Implications

Expand Down Expand Up @@ -119,9 +119,6 @@ Crawling through [sbc-bench results collection](../Results.md) comparing +30 dif
| [S922X](http://ix.io/3MuT) | 1900 | 1085350 | 571 |
| [A311D2](http://ix.io/3Wq0) | 2200 | 1252070 | 569 |
| [A311D](http://ix.io/3VfL) | 2400 | 1365900 | 569 |
| Neoverse-N1 | | | |
| [Ampere Altra](http://ix.io/4dsC) | 3000 | 1706150 | 569 |
| [Amazon m6g.8xlarge](http://ix.io/2FrG) | 2500 | 1424770 | 570 |
| Cortex-A76 | | | |
| [RK3588](http://ix.io/3XzI) | 985 | 560200 | 569 |
| [RK3588s](http://ix.io/3XYo) | 2330 | 1325370 | 569 |
Expand All @@ -130,5 +127,10 @@ Crawling through [sbc-bench results collection](../Results.md) comparing +30 dif
| [QRB5165](http://ix.io/49kx) | 2840 | 1598490 | 563 |
| Cortex-A78AE | | | |
| [NVIDIA Orin](http://ix.io/4ax9) | 2200 | 1242940 | 565 |
| Qualcomm Falkor V1 | | | |
| [Snapdragon 835](http://ix.io/4fea) | 2360 | 1342240 | 569 |
| Neoverse-N1 | | | |
| [Ampere Altra](http://ix.io/4dsC) | 3000 | 1706150 | 569 |
| [Amazon m6g.8xlarge](http://ix.io/2FrG) | 2500 | 1424770 | 570 |


Loading

0 comments on commit f27fceb

Please sign in to comment.