From: Olivier Matz <olivier.matz@6wind.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] mbuf autotest fails with 19.11-rc3
Date: Fri, 22 Nov 2019 10:51:57 +0100 [thread overview]
Message-ID: <20191122095157.GG8680@platinum> (raw)
In-Reply-To: <BYAPR18MB2424591A8D0DFE6515D845F3C84E0@BYAPR18MB2424.namprd18.prod.outlook.com>
Hi Jerin,
On Thu, Nov 21, 2019 at 12:24:24PM +0000, Jerin Jacob Kollanukkaran wrote:
> mbuf autotest fails with 19.11-rc3
>
> $ echo "mbuf_autotest" | sudo ./build/app/test/dpdk-test -c 0x3
>
> EAL: Detected 56 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'PA'
> EAL: No available hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> EAL: PCI device 0000:01:00.0 on NUMA socket 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:01:00.1 on NUMA socket 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> APP: HPET is not enabled, using TSC as default timer
> RTE>>mbuf_autotest
> Test mbuf dynamic fields and flags
> Reserved fields:
> Reserved flags:
> Free space in mbuf (0 = free, value = zone alignment):
> 0000: 00 00 00 00 00 00 00 00
> 0008: 00 00 00 00 00 00 00 00
> 0010: 00 00 00 00 00 00 00 00
> 0018: 00 00 00 00 00 00 00 00
> 0020: 00 00 00 00 00 00 00 00
> 0028: 00 00 00 00 00 00 00 00
> 0030: 00 00 00 00 00 00 00 00
> 0038: 00 00 00 00 00 00 00 00
> 0040: 00 00 00 00 00 00 00 00
> 0048: 00 00 00 00 00 00 00 00
> 0050: 00 00 00 00 00 00 00 00
> 0058: 00 00 00 00 00 00 00 00
> 0060: 00 00 00 00 00 00 00 00
> 0068: 00 00 00 00 00 00 00 00
> 0070: 10 10 10 10 10 10 10 10
> 0078: 10 10 10 10 10 10 10 10
> dynfield: offset=112, offset2=114, offset3=120
> dynflag: flag=23, flag2=24, flag3=40
> Reserved fields:
> name=test-dynfield offset=112 size=1 align=1 flags=0
> name=test-dynfield2 offset=114 size=2 align=2 flags=0
> name=test-dynfield3 offset=120 size=1 align=1 flags=0
> Reserved flags:
> name=test-dynflag bitnum=23 flags=0
> name=test-dynflag2 bitnum=24 flags=0
> name=test-dynflag3 bitnum=40 flags=0
> Free space in mbuf (0 = free, value = zone alignment):
> 0000: 00 00 00 00 00 00 00 00
> 0008: 00 00 00 00 00 00 00 00
> 0010: 00 00 00 00 00 00 00 00
> 0018: 00 00 00 00 00 00 00 00
> 0020: 00 00 00 00 00 00 00 00
> 0028: 00 00 00 00 00 00 00 00
> 0030: 00 00 00 00 00 00 00 00
> 0038: 00 00 00 00 00 00 00 00
> 0040: 00 00 00 00 00 00 00 00
> 0048: 00 00 00 00 00 00 00 00
> 0050: 00 00 00 00 00 00 00 00
> 0058: 00 00 00 00 00 00 00 00
> 0060: 00 00 00 00 00 00 00 00
> 0068: 00 00 00 00 00 00 00 00
> 0070: 00 01 00 00 04 04 04 04
> 0078: 00 01 02 02 04 04 04 04
> cannot allocate mbuf pool
> Test Failed
Could you please share some details about your configuration?
(amount of memory, arch, ...)
On my platform the test works, except if I use a very low amount
of memory (few MBs).
Thanks,
Olivier
next prev parent reply other threads:[~2019-11-22 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 12:24 [dpdk-dev] mbuf autotest fails with 19.11-rc3 Jerin Jacob Kollanukkaran
2019-11-22 9:51 ` Olivier Matz [this message]
2019-11-22 13:06 ` Jerin Jacob
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=20191122095157.GG8680@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
/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.