* [dpdk-dev] DPDK 17.11.4 (Madvise)Transparent Huge pages
@ 2019-01-02 15:31 chetan bhasin
2019-01-08 10:31 ` Burakov, Anatoly
0 siblings, 1 reply; 4+ messages in thread
From: chetan bhasin @ 2019-01-02 15:31 UTC (permalink / raw)
To: dev
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] DPDK 17.11.4 (Madvise)Transparent Huge pages
2019-01-02 15:31 [dpdk-dev] DPDK 17.11.4 (Madvise)Transparent Huge pages chetan bhasin
@ 2019-01-08 10:31 ` Burakov, Anatoly
2019-01-08 13:15 ` chetan bhasin
0 siblings, 1 reply; 4+ messages in thread
From: Burakov, Anatoly @ 2019-01-08 10:31 UTC (permalink / raw)
To: chetan bhasin, dev
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] DPDK 17.11.4 (Madvise)Transparent Huge pages
2019-01-08 10:31 ` Burakov, Anatoly
@ 2019-01-08 13:15 ` chetan bhasin
2019-01-08 16:10 ` Burakov, Anatoly
0 siblings, 1 reply; 4+ messages in thread
From: chetan bhasin @ 2019-01-08 13:15 UTC (permalink / raw)
To: Burakov, Anatoly; +Cc: dev
Thanks Anatoly
On Tue, Jan 8, 2019, 16:01 Burakov, Anatoly <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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] DPDK 17.11.4 (Madvise)Transparent Huge pages
2019-01-08 13:15 ` chetan bhasin
@ 2019-01-08 16:10 ` Burakov, Anatoly
0 siblings, 0 replies; 4+ messages in thread
From: Burakov, Anatoly @ 2019-01-08 16:10 UTC (permalink / raw)
To: chetan bhasin; +Cc: dev
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-01-08 16:10 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-02 15:31 [dpdk-dev] DPDK 17.11.4 (Madvise)Transparent Huge pages chetan bhasin
2019-01-08 10:31 ` Burakov, Anatoly
2019-01-08 13:15 ` chetan bhasin
2019-01-08 16:10 ` Burakov, Anatoly
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).