From: Michael Santana Francisco <msantana@redhat.com>
To: dev@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] Hugepages not being deleted
Date: Mon, 29 Apr 2019 14:28:35 -0400 [thread overview]
Message-ID: <8fc82f3d-4ba5-d5e2-b931-f2e690093364@redhat.com> (raw)
In-Reply-To: <2e847465-48d3-4df7-6a2c-e9903d131219@redhat.com>
ping
> Hello,
>
> I am currently working on a patch to fix the eal_flags_autotest test
> as it currently fails on many platforms.
> I have made some progress, however I stumbled upon a possible issue
> with EAL and hugepages.
> Looking at the code and some documentation it appears to me that
> hupepages are supposed to be automatically deleted on dynamic memory
> mode as the dpdk process exits.
> The test however reports that this is not happening.
>
> This can be shown by:
>
> bash# export DPDK_TEST=eal_flags_autotest
> bash# ./build/app/test/dpdk-test
> ...
> Error - hugepage files for memtest1 were not deleted!
> Error in test_file_prefix()
> Test Failed
> bash# ls /dev/hugepages/ #hugetlbfs is mounted on /dev/hugepages
> memtest1map_0 memtest1map_1 memtest1map_2 memtest1map_3
> memtest1map_4 memtest1map_5 memtest1map_6 memtest1map_7
> memtest1map_8 rtemap_0
>
> To me it appears that the hugepages are in fact not being deleted
> correctly.
> Is this an anomaly or is anyone else seeing this issue as well?
>
> Michael Santana
>
>
> Note, if you are running on a system with less than 8 cores please see
> patch
> https://github.com/Maickii/dpdk-2/commit/7cfad856611e3ded4050f670ec11d1b2e17851d8.patch
>
next prev parent reply other threads:[~2019-04-29 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 15:15 Michael Santana Francisco
2019-04-23 15:15 ` Michael Santana Francisco
2019-04-29 18:28 ` Michael Santana Francisco [this message]
2019-04-29 18:28 ` Michael Santana Francisco
2019-04-30 9:32 ` Burakov, Anatoly
2019-04-30 9:32 ` Burakov, Anatoly
2019-05-17 14:06 ` David Marchand
2019-05-20 10:43 ` Burakov, Anatoly
2019-05-20 11:09 ` David Marchand
2019-05-20 11:45 ` Burakov, Anatoly
2019-05-20 11:48 ` David Marchand
2019-05-20 15:08 ` Carrillo, Erik G
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=8fc82f3d-4ba5-d5e2-b931-f2e690093364@redhat.com \
--to=msantana@redhat.com \
--cc=anatoly.burakov@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).