From: David Marchand <david.marchand@redhat.com>
To: Shanmugasundaram M <shansirtt@gmail.com>
Cc: dev <dev@dpdk.org>, Olivier Matz <olivier.matz@6wind.com>,
Guillaume Gaudonville <guillaume.gaudonville@6wind.com>,
Jean-Mickael Guerin <jmg@6wind.com>
Subject: Re: [dpdk-dev] Reg 6Wind fastpath DPDK 18.11.1 virtual memory allocation ( 54.5GB of anonymous mapping)
Date: Wed, 9 Jun 2021 14:28:04 +0200 [thread overview]
Message-ID: <CAJFAV8wRyWSd=WP-LqSd6_YSXg+dfTzj5BKEFUTsUG5r5siwuA@mail.gmail.com> (raw)
In-Reply-To: <CALLOm0N8SEedqUXB406xyrGUU8Y_VOS9Hjnr_berNzcZJ3jiCw@mail.gmail.com>
On Wed, Jun 9, 2021 at 2:02 PM Shanmugasundaram M <shansirtt@gmail.com> wrote:
> We are using 6Wind fastpath(fp-rte) which is using DPDK version 18.11.1.
> We are seeing 65.5G(preallocated during startup) of virtual memory for
> fp-rte on a 32GB machine, 10G of that was huge pages (5000 mappings of 2M.)
>
> We found 4 strange anon (4K size) segments totaling 54.5G (16+16+16+6.5).
> Note: we changed / customized memory CONFIG_RTE_MAX_MEMSEG_PER_LIST=24576
> and default value of CONFIG_RTE_MAX_MEMSEG_LISTS=64 used.
> Kindly let us know
> 1. Why are allocating 54.5 GB anonymous mapping
> 2. When will we use it ?
This is likely pre-reserved virtual memory from the DPDK allocator.
This virtual memory won't probably never be used.
But you'd better ask 6WIND guys as they maintain their own DPDK downstream.
Copying a few guys.
--
David Marchand
next prev parent reply other threads:[~2021-06-09 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 19:00 [dpdk-dev] Reg DPDK EAL log-level=8 options is not throwing any DEBUG messages in /var/log/messages Shanmugasundaram M
2021-03-09 20:29 ` Stephen Hemminger
2021-03-10 18:19 ` Shanmugasundaram M
2021-03-10 18:25 ` Stephen Hemminger
2021-03-10 18:32 ` Shanmugasundaram M
2021-06-09 12:02 ` [dpdk-dev] Reg 6Wind fastpath DPDK 18.11.1 virtual memory allocation ( 54.5GB of anonymous mapping) Shanmugasundaram M
2021-06-09 12:28 ` David Marchand [this message]
2021-06-09 12:46 ` Bruce Richardson
2021-06-10 7:17 ` Olivier Matz
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='CAJFAV8wRyWSd=WP-LqSd6_YSXg+dfTzj5BKEFUTsUG5r5siwuA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=guillaume.gaudonville@6wind.com \
--cc=jmg@6wind.com \
--cc=olivier.matz@6wind.com \
--cc=shansirtt@gmail.com \
/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).