From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: chetan bhasin <chetan.bhasin017@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK 17.11.4 (Madvise)Transparent Huge pages
Date: Tue, 8 Jan 2019 16:10:45 +0000 [thread overview]
Message-ID: <d39e4a14-9618-36fa-6433-5cd7e42f44e9@intel.com> (raw)
In-Reply-To: <CACZZ+Y61RWYRSCQ5QfUHMUrk3+fmPfp1yqaHZw1J_kv=2hQjPQ@mail.gmail.com>
On 08-Jan-19 1:15 PM, chetan bhasin wrote:
> Thanks Anatoly
>
> On Tue, Jan 8, 2019, 16:01 Burakov, Anatoly <anatoly.burakov@intel.com
> <mailto:anatoly.burakov@intel.com> wrote:
>
> On 02-Jan-19 3:31 PM, chetan bhasin wrote:
> > Hi,
> >
> > I am using DPDK 17.11.4 version . Do anybody have idea that DPDK
> is using
> > benefit of Transparent huge-pages in case of Madvise.
> >
> > Thanks,
> > Chetan Bhasin
> >
>
> Hi,
>
> DPDK does not use MADVISE flags to allocate its hugepages - it
> allocates
> hugepages explicitly [1] [2].
>
> [1]
> http://git.dpdk.org/dpdk/tree/lib/librte_eal/linuxapp/eal/eal_memalloc.c#n367
> [2]
> http://git.dpdk.org/dpdk/tree/lib/librte_eal/linuxapp/eal/eal_memory.c#n336
>
> --
> Thanks,
> Anatoly
>
Apologies, i didn't notice that the question was about 17.11, so the
source code links are incorrect. However, the answer itself is still
correct - we always did allocate hugepages directly, and we never used
MADVISE flags.
--
Thanks,
Anatoly
prev parent reply other threads:[~2019-01-08 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 15:31 chetan bhasin
2019-01-08 10:31 ` Burakov, Anatoly
2019-01-08 13:15 ` chetan bhasin
2019-01-08 16:10 ` Burakov, Anatoly [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=d39e4a14-9618-36fa-6433-5cd7e42f44e9@intel.com \
--to=anatoly.burakov@intel.com \
--cc=chetan.bhasin017@gmail.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).