From: Stephen Hemminger <stephen@networkplumber.org>
To: Sakthivel Subramaniam <sakthivelpvs@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Regarding rte_malloc and linux malloc
Date: Thu, 9 Feb 2017 21:01:01 -0800 [thread overview]
Message-ID: <20170209210101.07a88c9f@xeon-e3> (raw)
In-Reply-To: <CANrG1jXoa_EnxgK-uCrsvQBxSZ80MV6syApV2oSh6a56x76HKw@mail.gmail.com>
On Fri, 10 Feb 2017 10:00:33 +0530
Sakthivel Subramaniam <sakthivelpvs@gmail.com> wrote:
> Hi,
> I have some basic doubt about DPDK memory allocation.
> 1. rte_malloc will allocate memory from hugepage memory ?
yes. but remember hugepage memory is limited
> 2. If we use normal malloc, this will be allocated from heap. will this
> allocation also useful for dpdk?
DPDK primary application can use it but you can't pass that memory
to a secondary DPDK process. Also you can't use malloc memory for things
that get DMA'd like packet buffers.
> 3. Or for better performance we have to use only rte_malloc?
The memory from rte_malloc will cause less TLB misses, but on a modern
processor for a small resident set size it probably makes no difference.
prev parent reply other threads:[~2017-02-10 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 4:30 Sakthivel Subramaniam
2017-02-10 5:01 ` 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=20170209210101.07a88c9f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=sakthivelpvs@gmail.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).