From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Asaf Sinai <AsafSi@Radware.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES: no difference in memory pool allocations, when enabling/disabling this configuration
Date: Mon, 26 Nov 2018 11:43:52 +0000 [thread overview]
Message-ID: <518f9333-8d80-0fa2-d391-b4c8df181508@intel.com> (raw)
In-Reply-To: <DB7PR01MB46354E3319774CC0EF16ED51CCD70@DB7PR01MB4635.eurprd01.prod.exchangelabs.com>
On 26-Nov-18 11:33 AM, Asaf Sinai wrote:
> Hi Anatoly,
>
> We did not check it with "testpmd", only with our application.
> From the beginning, we did not enable this configuration (look at attached files), and everything works fine.
> Of course we rebuild DPDK, when we change configuration.
> Please note that we use DPDK 17.11.3, maybe this is why it works fine?
Just tested with DPDK 17.11, and yes, it does work the way you are
describing. This is not intended behavior. I will look into it.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-11-26 11:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 9:15 Asaf Sinai
2018-11-26 11:09 ` Burakov, Anatoly
2018-11-26 11:33 ` Asaf Sinai
2018-11-26 11:43 ` Burakov, Anatoly [this message]
2018-11-26 12:50 ` Burakov, Anatoly
2018-11-26 13:16 ` Ilya Maximets
2018-11-26 13:20 ` Ilya Maximets
2018-11-26 13:42 ` Burakov, Anatoly
2018-11-26 14:10 ` Ilya Maximets
2018-11-26 14:21 ` Burakov, Anatoly
2018-11-26 14:32 ` Ilya Maximets
2018-11-26 14:57 ` Burakov, Anatoly
2018-11-26 15:25 ` Asaf Sinai
2018-11-27 10:26 ` Hemant Agrawal
2018-11-27 10:33 ` Burakov, Anatoly
2018-11-27 16:49 ` Ilya Maximets
2018-12-09 8:14 ` Asaf Sinai
2018-12-10 10:09 ` Burakov, Anatoly
2018-12-16 9:44 ` Asaf Sinai
[not found] ` <CGME20181126122321eucas1p1c8bfe7e1b74fc5cd71eec3a3c8929f5d@eucas1p1.samsung.com>
2018-11-26 12:23 ` [dpdk-dev] CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES: no difference in memory pool allocations Ilya Maximets
2018-11-26 12:46 ` Ilya Maximets
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=518f9333-8d80-0fa2-d391-b4c8df181508@intel.com \
--to=anatoly.burakov@intel.com \
--cc=AsafSi@Radware.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).