Ten64 (8xCortex-A53) testing on Debian 10 (mainline 5.8 kernel)
Processor: ARMv8 Cortex-A53 @ 1.60GHz (8 Cores), Motherboard: traverse ten64 (2020.07-rc1-00404-g175d0de361-dirty BIOS), Memory: 3584MB, Disk: 230GB M.2 (P42) 3TE2 + 4 x 500GB Samsung SSD 860
OS: Debian 10, Kernel: 5.8.16-traverse-stable-5-8+136-00001-gd4b7f859a (aarch64), Compiler: GCC 8.3.0, File-System: ext4
Processor Notes: Scaling Governor: qoriq_cpufreq performance
Security Notes: itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + spec_store_bypass: Not affected + spectre_v1: Mitigation of __user pointer sanitization + spectre_v2: Not affected + srbds: Not affected + tsx_async_abort: Not affected
This is a benchmark of the WireGuard secure VPN tunnel and Linux networking stack stress test. The test runs on the local host but does require root permissions to run. The way it works is it creates three namespaces. ns0 has a loopback device. ns1 and ns2 each have wireguard devices. Those two wireguard devices send traffic through the loopback device of ns0. The end result of this is that tests wind up testing encryption and decryption at the same time -- a pretty CPU and scheduler-heavy workflow. Learn more via the OpenBenchmarking.org test page.
Processor: ARMv8 Cortex-A53 @ 1.60GHz (8 Cores), Motherboard: traverse ten64 (2020.07-rc1-00404-g175d0de361-dirty BIOS), Memory: 3584MB, Disk: 230GB M.2 (P42) 3TE2 + 4 x 500GB Samsung SSD 860
OS: Debian 10, Kernel: 5.8.16-traverse-stable-5-8+136-00001-gd4b7f859a (aarch64), Compiler: GCC 8.3.0, File-System: ext4
Processor Notes: Scaling Governor: qoriq_cpufreq performance
Security Notes: itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + spec_store_bypass: Not affected + spectre_v1: Mitigation of __user pointer sanitization + spectre_v2: Not affected + srbds: Not affected + tsx_async_abort: Not affected
Testing initiated at 20 October 2020 05:54 by user root.