On Sun, May 12, 2024 at 12:31:24AM -0700, Eric Biggers wrote: > Table 3: VAES-based AES-256-GCM encryption throughput in MB/s, > implementation name vs. message length in bytes: > > | 16384 | 4096 | 4095 | 1420 | 512 | 500 | > ---------------------+-------+-------+-------+-------+-------+-------+ > This implementation | 13139 | 12070 | 11466 | 8999 | 6949 | 6048 | > AVX512_Intel_OpenSSL | 12927 | 11499 | 10976 | 8375 | 5386 | 5853 | > AVX512_Intel_Linux | 12656 | 11263 | 10779 | 7958 | 5592 | 5029 | > AVX512_Cloudflare | 11120 | 10186 | 10075 | 4856 | 4919 | 4786 | > > | 300 | 200 | 64 | 63 | 16 | > ---------------------+-------+-------+-------+-------+-------+ > This implementation | 4709 | 3512 | 1787 | 1765 | 714 | > AVX512_Intel_OpenSSL | 4157 | 4071 | 2493 | 2132 | 1042 | > AVX512_Intel_Linux | 3535 | 2686 | 1416 | 1203 | 572 | > AVX512_Cloudflare | 3062 | 1110 | 1042 | 1028 | 169 | > Note, some of the AVX512_Cloudflare numbers were slightly off, and I've fixed this in v3. v3 also includes another small optimization. - Eric
