From: Koji Ikeura <ikeura@fnsc.co.jp>
To: users@dpdk.org
Subject: Low crypto performance of AES-NI MB PMD on multi-core
Date: Wed, 5 Oct 2022 13:50:39 +0900 [thread overview]
Message-ID: <4dace3f1-bb0a-5fc0-e73f-f9fa5d1f555a@fnsc.co.jp> (raw)
Hi,
I am using dpdk-test-crypto-perf to measure the crypto performance of AES-NI MB PMD.
The performance reports say "The SW PMD performance is linear scaling out with core numbers",
but there are no result on multiple cores and this is not the case in my environment.
What about your environment? Does anyone know how to improve it?
With DPDK v22.07/intel-ipsec-mb v1.20 and DPDK v22.11/intel-ipsec-mb v1.00 the performance
did not scale out with the number of cores, but with DPDK v17.05.2/intel-ipsec-mb v0.45
the performance do scaled out with the number of cores.
Results and environment are below.
# Results (DPDK v22.07 / intel-ipsec-mb v1.20)
- 8 cores
$ ./dpdk-test-crypto-perf -l 0-8 --vdev crypto_aesni_mb_pmd -- --ptest throughput --devtype crypto_aesni_mb --optype cipher-then-auth --cipher-algo aes-cbc --cipher-op encrypt --cipher-key-sz 16 --auth-algo sha1-hmac --auth-op generate --auth-key-sz 64 --digest-sz 12 --total-ops 10000000 --burst-sz 32 --buffer-sz 64
lcore id Buf Size Burst Size Enqueued Dequeued Failed Enq Failed Deq MOps Gbps Cycles/Buf
8 64 32 10000000 10000000 0 0 1.8980 0.9718 1053.74
7 64 32 10000000 10000000 0 0 1.9231 0.9846 1040.01
5 64 32 10000000 10000000 0 0 1.8613 0.9530 1074.49
3 64 32 10000000 10000000 0 0 1.8205 0.9321 1098.62
1 64 32 10000000 10000000 0 0 1.7988 0.9210 1111.86
2 64 32 10000000 10000000 0 0 1.7988 0.9210 1111.88
6 64 32 10000000 10000000 0 0 1.6651 0.8525 1201.14
4 64 32 10000000 10000000 0 0 1.6618 0.8508 1203.52
- 1 core
$ ./dpdk-test-crypto-perf -l 0-1 --vdev crypto_aesni_mb_pmd -- --ptest throughput --devtype crypto_aesni_mb --optype cipher-then-auth --cipher-algo aes-cbc --ciph
er-op encrypt --cipher-key-sz 16 --auth-algo sha1-hmac --auth-op generate --auth-key-sz 64 --digest-sz 12 --total-ops 10000000 --burst-sz 32 --buffer-sz 64
lcore id Buf Size Burst Size Enqueued Dequeued Failed Enq Failed Deq MOps Gbps Cycles/Buf
1 64 32 10000000 10000000 0 0 5.7756 2.9571 346.28
# Environments
- CPU
Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
- OS
Oracle Linux Server 8.4
- Kernel
4.18.0-240.el8.x86_64
- DPDK and intel-ipsec-mb version
DPDK intel-ipsec-mb
v22.07 v1.20 <-- do not scale out
v20.11.3 v1.00 <-- do not scale out
v17.05.2 v0.45 <-- scale out
--
Koji Ikeura
next reply other threads:[~2022-10-05 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 4:50 Koji Ikeura [this message]
2022-12-05 9:04 ` De Lara Guarch, Pablo
2022-12-05 9:24 ` Koji Ikeura
2022-12-14 11:33 ` De Lara Guarch, Pablo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4dace3f1-bb0a-5fc0-e73f-f9fa5d1f555a@fnsc.co.jp \
--to=ikeura@fnsc.co.jp \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).