From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 843] [dpdk-21.11 rc1] performance tests with QAT are failing
Date: Wed, 27 Oct 2021 17:47:33 +0000 [thread overview]
Message-ID: <bug-843-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=843
Bug ID: 843
Summary: [dpdk-21.11 rc1] performance tests with QAT are
failing
Product: DPDK
Version: 21.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: cryptodev
Assignee: dev@dpdk.org
Reporter: varalakshmi.s@intel.com
Target Milestone: ---
Environment
DPDK Version: 6c390cee976e33b1e9d8562d32c9d3ebe5d9ce94
OS: 5.4.0-89-generic #100~18.04.1-Ubuntu SMP Wed Sep 29 10:59:42 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Compiler: 7.5.0
Hardware platform: Purley
Steps to reproduce
from dpdk path, the following steps should be followed:
x86_64-native-linuxapp-gcc/app/dpdk-test-crypto-perf -l 9,10,66,11,67,12,68 -a
0000:1a:01.0 -a 0000:1a:01.1 -a 0000:1a:02.2 -a 0000:1a:02.3 -a 0000:1a:02.4 -a
0000:1a:02.5 --socket-mem 2048,0 -n 4 – --ptest throughput --silent --total-ops
30000000 --burst-sz 32 --buffer-sz 64,128,256,512,1024,2048 --devtype
crypto_qat --optype cipher-then-auth --cipher-algo aes-cbc --cipher-op encrypt
--cipher-key-sz 16 --cipher-iv-sz 16 --auth-algo sha1-hmac --auth-op generate
--auth-key-sz 64 --digest-sz 20
Actual Result:
27/10/2021 23:55:00 dut.10.240.183.147: EAL: Detected CPU lcores: 112^M
EAL: Detected NUMA nodes: 2^M
EAL: Detected static linkage of DPDK^M
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket^M
EAL: Selected IOVA mode 'VA'^M
EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs found
for that size^M
EAL: VFIO support initialized^M
EAL: Using IOMMU type 1 (Type 1)^M
EAL: Error setting up interrupts!^M
EAL: 0000:1a:01.0 setup device failed^M
EAL: Requested device 0000:1a:01.0 cannot be used^M
EAL: 0000:1a:01.1 failed to select IOMMU type^M
EAL: Requested device 0000:1a:01.1 cannot be used^M
EAL: 0000:1a:02.2 failed to select IOMMU type^M
EAL: Requested device 0000:1a:02.2 cannot be used^M
EAL: 0000:1a:02.3 failed to select IOMMU type^M
EAL: Requested device 0000:1a:02.3 cannot be used^M
EAL: 0000:1a:02.4 failed to select IOMMU type^M
EAL: Requested device 0000:1a:02.4 cannot be used^M
EAL: 0000:1a:02.5 failed to select IOMMU type^M
EAL: Requested device 0000:1a:02.5 cannot be used^M
EAL: Bus (pci) probe failed.^M
Expected Result
Test is expected to Pass with no errors.
Stack Trace or Log
------------------------------------------------------------------------------
8cb5d08db940a6b26f5c5ac03b49bac25e9a7022 is the first bad commit commit
8cb5d08db940a6b26f5c5ac03b49bac25e9a7022
Author: Harman Kalra <hkalra@marvell.com>
Date: Sat Oct 23 02:19:32 2021 +0530
interrupts: extend event list
Dynamically allocating the efds and elist array of intr_handle
structure, based on size provided by user. Eg size can be
MSIX interrupts supported by a PCI device.
Signed-off-by: Harman Kalra <hkalra@marvell.com>
Signed-off-by: David Marchand <david.marchand@redhat.com>
Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Tested-by: Raslan Darawsheh <rasland@nvidia.com>
------------------------------------------------------------------------------
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-10-27 17:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-843-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.