Hi JJK, Yeah, I know this way, but there is still context switching in the kernel space and user space. I have been looking for a way to benchmark in the kernel space. I expect there is a kernel module like below:
insmod benchmark.ko AES-256-GCM (After it's done, this module will exit automatically) Tony Jan Just Keijser <jan.just.keij...@gmail.com> 于2022年4月5日周二 19:26写道： > > hi Tony, > > On 02/04/22 11:40, Tony He wrote: > > Hi Antonio, > > > > I am porting ovpn-dco to embedded ARMv8 device with hardware crypto > > engine. However the performance is not very good. > > It's about 130-140Mbps. I expect more. The SDK already provides kernel > > CryptoAPI(CFI) interface to access the crypto engine. > > I want to know if the crypto operation is the bottleneck. Do you know > > how to benchmark crypto performance in the kernel space? > > Any advice is welcome. Thank you! > > > a quick & dirty way to test the hardware crypto engine is to use the > Linux cryptodev engine in combination with openssl ; it's a bit tricky > to get it working but it *is* a nice way to test hardware crypto. > > * https://github.com/cryptodev-linux/cryptodev-linux.git > * do a custom openssl build with > ./Configure -DHAVE_CRYPTODEV -DUSE_CRYPTODEV_DIGESTS enable-engine > enable-dso enable-devcryptoeng <platform> > * run openssl speed using > ./openssl speed -elapsed -engine devcrypto -evp aes-128-cbc > > and compare the results with "-engine devcrypto" removed. > > HTH, > > JJK > > > _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
