All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/vhost/virtio Bug 1849] [dpdk-22.11.11rc1] virtio_perf_cryptodev_func/test_virtio_aes_cbc_sha1_hmac: dpdk-test-crypto-perf EAL: Error: Invalid memory
Date: Wed, 10 Dec 2025 07:25:44 +0000	[thread overview]
Message-ID: <bug-1849-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1849

            Bug ID: 1849
           Summary: [dpdk-22.11.11rc1]
                    virtio_perf_cryptodev_func/test_virtio_aes_cbc_sha1_hm
                    ac: dpdk-test-crypto-perf EAL: Error: Invalid memory
           Product: DPDK
           Version: 22.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: vhost/virtio
          Assignee: dev@dpdk.org
          Reporter: yux.jiang@intel.com
  Target Milestone: ---

Reproduce Step:

[Environment]

DPDK version: v22.11.11rc1

commit 8ab51c7334ee8958d2a7a16ee35808df64c83695 (HEAD -> 22.11, origin/22.11)
Author: Radu Nicolau <radu.nicolau@intel.com>
Date:   Mon Dec 8 12:45:15 2025 +0000    "crypto/qat: fix backported patch   
Backported patch below was applied to the wrong QAT function.    Fixes:
96a4318baabd ("crypto/qat: fix out-of-place chain/cipher/auth headers")   
Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>commit
12b1ff867e6f508462720cb00c2b3ffafcb7068a (tag: v22.11.11-rc1)
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date:   Thu Dec 4 00:49:08 2025 +0000    version: 22.11.11-rc1   
Signed-off-by: Luca Boccassi <luca.boccassi@gmail.com>


[Test Setup]

1, Build dpdk
rm -rf x86_64-native-linuxapp-gcc
CC=gcc meson -Denable_kmods=False -Dlibdir=lib --default-library=static
x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
meson configure -Dexamples=vhost_crypto x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc

2, Bind 1 NIC VF to dpdk
echo 1 > /sys/bus/pci/devices/0000\:3b\:00.0/sriov_numvfs
usertools/dpdk-devbind.py --bind=vfio-pci 0000:3b:02.0

3, Start vhost_crypto
rm -r /tmp/*
x86_64-native-linuxapp-gcc/examples/dpdk-vhost_crypto -l 1,2,3 -a 0000:00:00.0
--vdev crypto_aesni_mb_pmd_1 --socket-mem 2048,0 -n 4 -- --config
"(2,0,0),(3,0,0)" --socket-file 2,/tmp/vm0_crypto0.sock
--socket-file=3,/tmp/vm0_crypto1.sock

4, Start VM

lsof -n -i:6600
taskset -c 11,12,13,14 /root/qemu-2.12/bin/qemu-system-x86_64  -name vm0
-enable-kvm -pidfile /tmp/.vm0.pid \
-daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait -device
e1000,netdev=nttsip1  \
-netdev user,id=nttsip1,hostfwd=tcp:10.239.252.147:6600-:22 -device
vfio-pci,host=0000:3b:02.0,id=pt_0 \
-cpu host -smp 4 -m 4096 -object
memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on \
-numa node,memdev=mem -mem-prealloc -vnc :1 \
-chardev socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 -device
virtio-serial -device
virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 \
-chardev socket,path=/tmp/vm0_crypto0.sock,id=vm0_crypto0 -object
cryptodev-vhost-user,id=cryptodev0,chardev=vm0_crypto0 -device
virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0 \
-chardev socket,path=/tmp/vm0_crypto1.sock,id=vm0_crypto1 -object
cryptodev-vhost-user,id=cryptodev1,chardev=vm0_crypto1 -device
virtio-crypto-pci,id=crypto1,cryptodev=cryptodev1 \
-drive file=/home/image/ubuntu2404.2.img

5, IN VM, set hugepage and set virtio device
modprobe uio_pci_generic    
lspci -d:1054|awk '{{print $1}}'      
echo 0000:00:07.0 > /sys/bus/pci/devices/0000\:00\:07.0/driver/unbind      
echo 0000:00:06.0 > /sys/bus/pci/devices/0000\:00\:06.0/driver/unbind      
echo "1af4 1054" > /sys/bus/pci/drivers/uio_pci_generic/new_id  
awk '/Hugepagesize/ {print $2}' /proc/meminfo      
echo 0 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages      
echo 1024 >
/sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages

6, IN VM, run Test Case test_virtio_aes_cbc_sha1_hmac
x86_64-native-linuxapp-gcc/app/dpdk-test-crypto-perf  -l 0,1 -a 00:06.0
--socket-mem 512,0 -n 4  -- --ptest throughput --silent  --total-ops 100000
--burst-sz 32 --buffer-sz 64,128,256,512,1024,2048 --devtype crypto_virtio
--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 12



[Actual Result]

VM: root@ub2404-2:~/dpdk# x86_64-native-linuxapp-gcc/app/dpdk-test-crypto-perf 
-l 0,1 -a 00:06.0 --socket-mem 512,0 -n 4  -- --ptest throughput --silent 
--total-ops 100000 --burst-sz 32 --buffer-sz 64,128,256,512,1024,2048 --devtype
crypto_virtio --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 12
EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: Probe PCI driver: crypto_virtio (1af4:1054) device: 0000:00:06.0 (socket
-1)
CRYPTODEV: Creating cryptodev 0000:00:06.0
CRYPTODEV: Initialisation parameters - name: 0000:00:06.0,socket id: -1, max
queue pairs: 0
Allocated pool "sess_mp_0" on socket 0
    lcore id    Buf Size  Burst Size    Enqueued    Dequeued  Failed Enq 
Failed Deq        MOps        Gbps  Cycles/Buf           1          64         
32      100000      100000      247186      258255      1.0802      0.5531    
2305.03
           1         128          32      100000      100000      384848     
384874      1.0093      1.0336     2466.95
           1         256          32      100000      100000      375349     
375371      0.8821      1.8064     2822.96
           1         512          32      100000      100000      381865     
430148      0.8622      3.5317     2887.86
           1        1024          32      100000      100000      795137     
826088      0.5592      4.5811     4452.69
           1        2048          32      100000      100000     1073023    
1088023      0.4712      7.7207     5283.97
EAL: Error: Invalid memory
EAL: Error: Invalid memory

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2025-12-10  7:25 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-1849-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.