From: Asaf Sinai <AsafSi@Radware.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES: no difference in memory pool allocations, when enabling/disabling this configuration
Date: Mon, 26 Nov 2018 09:15:51 +0000 [thread overview]
Message-ID: <DB7PR01MB4635B4B0B14F9CD1C135F3C1CCD70@DB7PR01MB4635.eurprd01.prod.exchangelabs.com> (raw)
Hi,
We have 2 NUMAs in our system, and we try to allocate a single DPDK memory pool on each NUMA.
However, we see no difference when enabling/disabling "CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES" configuration.
We expected that disabling it will allocate pools only on one NUMA (probably NUMA0), but it actually allocates pools on both NUMAs, according to "socket_id" parameter passed to "rte_mempool_create" API.
We have 192GB memory, so NUMA1 memory starts from address: 0x1800000000.
As you can see below, "undDpdkPoolNameSocket_1" was indeed allocated on NUMA1, as we wanted, although "CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES" is disabled:
CONFIG_RTE_LIBRTE_VHOST_NUMA=n
CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n
created poolName=undDpdkPoolNameSocket_0, nbufs=887808, bufferSize=2432, total=2059MB
(memZone: name=MP_undDpdkPoolNameSocket_0, socket_id=0, vaddr=0x1f2c0427d00-0x1f2c05abe00, paddr=0x178e627d00-0x178e7abe00, len=1589504, hugepage_sz=2MB)
created poolName=undDpdkPoolNameSocket_1, nbufs=887808, bufferSize=2432, total=2059MB
(memZone: name=MP_undDpdkPoolNameSocket_1, socket_id=1, vaddr=0x1f57fa7be40-0x1f57fbfff40, paddr=0x2f8247be40-0x2f825fff40, len=1589504, hugepage_sz=2MB)
Does anyone know what is "CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES" configuration used for?
Thanks,
Asaf
[Radware]
Asaf Sinai
ND SW Engineer
Email: asafsi@radware.com<mailto:asafsi@radware.com>
T:+972-72-3917050
M:+972-50-6518541
F:+972-3-6488662
[Check out the latest and greatest from Radware]<https://www.radware.com/Resources/CampaignRedirector.html>
www.radware.com<https://www.radware.com>
[Blog]<https://blog.radware.com/> [https://www.radware.com/images/signature/linkedin.jpg] <https://www.linkedin.com/companies/165642> [https://www.radware.com/images/signature/twitter.jpg] <file://twitter.com/radware> [youtube] <https://www.youtube.com/user/radwareinc>
Confidentiality note: This message, and any attachments to it, contains privileged/confidential information of RADWARE Ltd./RADWARE Inc. and may not be disclosed, used, copied, or transmitted in any form or by any means without prior written permission from RADWARE. If you are not the intended recipient, delete the message and any attachments from your system without reading or copying it, and kindly notify the sender by e-mail. Thank you.
P Please consider your environmental responsibility before printing this e-mail
next reply other threads:[~2018-11-26 9:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 9:15 Asaf Sinai [this message]
2018-11-26 11:09 ` Burakov, Anatoly
2018-11-26 11:33 ` Asaf Sinai
2018-11-26 11:43 ` Burakov, Anatoly
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=DB7PR01MB4635B4B0B14F9CD1C135F3C1CCD70@DB7PR01MB4635.eurprd01.prod.exchangelabs.com \
--to=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).