From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: eal_flags_autotest fails with tailq fully local
Date: Fri, 31 Oct 2014 16:39:05 +0100 [thread overview]
Message-ID: <2218255.iKClzEEk9y@xps13> (raw)
Hi,
Since release 1.7.1 and patchset "tailq fully local", the test
eal_flags_autotest doesn't work anymore. It fails because it doesn't
find any free hugepage (rte_memzone_reserve).
The interesting commits are:
http://dpdk.org/browse/dpdk/commit/?id=e3f3b68c6e42
http://dpdk.org/browse/dpdk/commit/?id=dd0024ccbc70
The test works only when these patches are reverted.
Here is how to reproduce:
git revert e3f3b68c6e42
git revert dd0024ccbc70
make config T=x86_64-native-linuxapp-gcc
make
mkdir -p /mnt/huge
mount -t hugetlbfs nodev /mnt/huge
echo 9 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
build/app/test -c 1 -n 1 -m 1
eal_flags_autotest
I'd like this regression to be fixed for the coming release.
If someone has an idea, he's welcome :)
Thanks
--
Thomas
next reply other threads:[~2014-10-31 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 15:39 Thomas Monjalon [this message]
2014-11-05 17:50 ` eal_flags_autotest fails with tailq fully local Thomas Monjalon
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=2218255.iKClzEEk9y@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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.