From: Anupam Kapoor <anupam.kapoor@gmail.com>
To: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Memory Allocation
Date: Tue, 16 May 2017 22:00:27 +0530 [thread overview]
Message-ID: <CAEXHiZGmS+vYyfBGQt1DtpNXvctivcJGkQrCAXEgtfs_wDRgvg@mail.gmail.com> (raw)
In-Reply-To: <D3DC9088-194A-4838-8E75-FBFD6A40117D@cloudsimple.com>
On Tue, May 16, 2017 at 9:44 PM, Kumaraparameshwaran Rathnavel <
krath@cloudsimple.com> wrote:
> will the memory be allocated on the Node where the DPDK thread was
> initially running when the memory allocation functions was called
rte_malloc(...) will return memory allocated on the NUMA socket of the
core which made the invokation. access to this from other locations will
incur the qpi penalty...
--
thanks
anupam
In the beginning was the lambda, and the lambda was with Emacs, and Emacs
was the lambda.
next 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 [this message]
2017-05-16 16:30 ` Stephen Hemminger
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=CAEXHiZGmS+vYyfBGQt1DtpNXvctivcJGkQrCAXEgtfs_wDRgvg@mail.gmail.com \
--to=anupam.kapoor@gmail.com \
--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).