From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 863] external_mempool_handler:execute mempool_autotest command failed on FreeBSD
Date: Fri, 29 Oct 2021 03:21:54 +0000 [thread overview]
Message-ID: <bug-863-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=863
Bug ID: 863
Summary: external_mempool_handler:execute mempool_autotest
command failed on FreeBSD
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: leweix.yang@intel.com
Target Milestone: ---
DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
21.11-rc1:6c390cee976e33b1e9d8562d32c9d3ebe5d9ce94
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: FreeBSD 13.0-RELEASE
Compiler: gcc (FreeBSD Ports Collection) 10.3.0
Hardware platform: Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz.
NIC hardware: Ethernet Controller X710 for 10GbE SFP+
Device version: 1.12.24
Test Setup
Steps to reproduce
List the steps to reproduce the issue:
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.lanch app
# ./x86_64-native-bsdapp-gcc/app/test/dpdk-test -n 4 -c f
3. execute dpdk command
# mempool_autotest
Show the output from the previous commands:
# common_pool_count=1598
no statistics available
EAL: Test assert
test_mempool_flag_non_io_unset_when_populated_with_valid_iova
line 781 failed: Cannot get IOVA
test failed at test_mempool():1030
Test Failed
Expected Result
Explain what is the expected result in text or as an example output:
# common_pool_count=2111
no statistics available
Test OK
Regression
Is this issue a regression: (Y/N) Y
git show 11541c5c81dd2b286132dbff8a8c324d7e9bc945
commit 11541c5c81dd2b286132dbff8a8c324d7e9bc945 (HEAD)
Author: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Date: Tue Oct 19 01:43:51 2021 +0300
mempool: add non-IO flag
Mempool is a generic allocator that is not necessarily used
for device IO operations and its memory for DMA.
Add MEMPOOL_F_NON_IO flag to mark such mempools automatically
a) if their objects are not contiguous;
b) if IOVA is not available for any object.
Other components can inspect this flag
in order to optimize their memory management.
Discussion: https://mails.dpdk.org/archives/dev/2021-August/216654.html
Signed-off-by: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-10-29 3:21 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-863-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.