https://bugs.dpdk.org/show_bug.cgi?id=1105
Bug ID: 1105
Summary: [dpdk-22.11] unit_tests_loopback: pmd_perf_autotest
failed
Product: DPDK
Version: 22.11
Hardware: All
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: linglix.c...@intel.com
Target Milestone: ---
Environment
OS: FreeBSD 13.1-RELEASE
Test Setup
1. build dpdk
CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static
x86_64-native-bsdapp-gcc
ninja -C x86_64-native-bsdapp-gcc
2.kldload ./x86_64-native-bsdapp-gcc/kernel/freebsd/contigmem.ko
kldload ./x86_64-native-bsdapp-gcc/kernel/freebsd/nic_uio.ko
3. launch testpmd
x86_64-native-bsdapp-gcc/app/test/dpdk-test -l 2-39 -n 4 -a 84:00.0 -a 84:00.1
4.start autotest
RTE>>pmd_perf_autotest
Show the output from the previous commands
Start PMD RXTX cycles cost test.
Allocated mbuf pool on socket 0
CONFIG RXD=1024 TXD=1024
No avail lcore to run test
Test Failed
Expected Result
Test OK
Regression
Is this issue a regression: (Y/N)Y
Version the regression was introduced: Specify git id if known.
commit 7dcd73e37965ba0bfa430efeac362fe183ed0ae2
Author: Olivier Matz <olivier.m...@6wind.com>
Date: Tue Oct 4 16:58:50 2022 +0200
drivers/bus: set device NUMA node to unknown by default
The dev->device.numa_node field is set by each bus driver for
every device it manages to indicate on which NUMA node this device lies.
When this information is unknown, the assigned value is not consistent
across the bus drivers.
Set the default value to SOCKET_ID_ANY (-1) by all bus drivers
when the NUMA information is unavailable. This change impacts
rte_eth_dev_socket_id() in the same manner.
Signed-off-by: Olivier Matz <olivier.m...@6wind.com>
--
You are receiving this mail because:
You are the assignee for the bug.
