Re: [PATCH v2 0/4] crypto: rockchip: Add RK356x/RK3588 cryptographic offloader
"Diederik de Haas" <[email protected]>
| Newsgroups | org.kernel.vger.linux-crypto,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-rockchip,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Tue Aug 18, 2026 at 10:04 PM CEST, Eric Biggers wrote: > tcrypt.c reports cycle counts from get_cycles(), which has an > architecture-dependent meaning. On x86_64 it is something approximating > the CPU cycles (3-5 GHz) whereas on arm64 it is the ARM Generic Timer > which tends to be around 24 MHz or so, over 100 times slower than the > actual CPU. So 9044 vs 115 "cycles" for x86_64 vs arm64 sounds about > expected, and they suggest the real times are likely similar but > slightly faster on x86_64 as expected. Phew, thanks for the explanation :-) > This sort of thing is why benchmarks usually should measure real time. > The legacy module tcrypt.c unfortunately uses get_cycles() instead. What would be a better/non-legacy way to test crypto performance? Is that documented somewhere? Cheers, Diederik