From: Stephen Hemminger <stephen@networkplumber.org>
To: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Memory Allocation
Date: Tue, 16 May 2017 09:30:40 -0700 [thread overview]
Message-ID: <20170516093040.44cc3e9e@xeon-e3> (raw)
In-Reply-To: <D3DC9088-194A-4838-8E75-FBFD6A40117D@cloudsimple.com>
On Tue, 16 May 2017 21:44:46 +0530
Kumaraparameshwaran Rathnavel <krath@cloudsimple.com> wrote:
> Hi All,
>
> When I have a system with NUMA enabled and say my application is running one DPDK thread and I use that thread for the memory allocation will the memory be physically allocated during the access time or will the memory be allocated on the Node where the DPDK thread was initially running when the memory allocation functions was called. So threads accessing the memory locations from the other nodes remotely will suffer a degradation in performance. Please correct me if I am wrong.
>
> Thanking You,
> Param.
>
>
Most of the memory allocation mechansisms (malloc, mmap) in Linux are not NUMA aware.
If you read the source (which is always the definitive place to look), for DPDK you
will see that rte_malloc, rte_mempool, and other routines have option to take a NUMA
node as argument. It is up to the application to determine what the "right" node is.
Often it is the node where the hardware is located (for mbuf pools), or the node
where the thread is running. But unless you lock the thread to a node, the scheduler
is likely to move it around under load.
prev parent reply other threads:[~2017-05-16 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 16:14 Kumaraparameshwaran Rathnavel
2017-05-16 16:30 ` Anupam Kapoor
2017-05-16 16:30 ` Stephen Hemminger [this message]
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=20170516093040.44cc3e9e@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=krath@cloudsimple.com \
--cc=users@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).