From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 494] rte_pktmbuf_pool_create returns EINVAL instead of ENOMEM in rte_errno when not enough huge pages memory
Date: Sat, 27 Jun 2020 18:28:13 +0000 [thread overview]
Message-ID: <bug-494-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=494
Bug ID: 494
Summary: rte_pktmbuf_pool_create returns EINVAL instead of
ENOMEM in rte_errno when not enough huge pages memory
Product: DPDK
Version: 19.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: alexander.pshenichnikov@gmail.com
Target Milestone: ---
DPDK: dpdk-stable-19.11.3
GCC: Ubuntu 7.5.0-3ubuntu1~18.04
OS: Ubuntu 18.04 LTS
Steps to reproduce:
1. Allocate total 32 huge pages of size 2048K
echo 32 >
/sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
2. Request testpmd to create 32768 mbufs
./build/app/testpmd -c7 --vdev=net_pcap,iface=net0 -- -i --nb-cores=1
--nb-ports=1 --total-num-mbufs=32768
3. Notice 'Invalid argument' in error description
testpmd: preferred mempool ops selected: ring_mp_mc
EAL: Error - exiting with code: 1
Cause: Creation of mbuf pool for socket 0 failed: Invalid argument
Expected result:
Error message should say
"Cause: Creation of mbuf pool for socket 0 failed: Cannot allocate memory"
i.e rte_errno should be EINVAL
Suspected commit:
commit 3a3d0c75b43e8d1670c5ea6bf85cb3e1e60dfa2b
Author: Olivier Matz <olivier.matz@6wind.com>
Date: Fri Jan 17 10:51:49 2020 +0100
mempool: fix slow allocation of large pools
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-06-27 18:28 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-494-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.