From: Stephen Hemminger <stephen@networkplumber.org>
To: David Aldrich <david.aldrich.ntml@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Basic hugepages question
Date: Wed, 9 Dec 2020 08:59:32 -0800 [thread overview]
Message-ID: <20201209085932.60a0f9ea@hermes.local> (raw)
In-Reply-To: <CAJK_iehq4qKvFeyTa5WR6Bb37NO8M-w_wdRmfi6Gwv_oMNvfsQ@mail.gmail.com>
On Wed, 9 Dec 2020 16:34:29 +0000
David Aldrich <david.aldrich.ntml@gmail.com> wrote:
> Hi
>
> Having successfully demonstrated using dpdk with our application, it's been
> pointed out to me that our settings are using a very large amount of memory.
>
> I am initialising the EAL with:
>
> -m 16000
>
> i.e. 16GB!
>
> However, I am only specifying a count of 0x4000 to rte_ring_create(), which
> I call twice to create one Rx and one Tx ring. So I guess these are only
> using 32MB RAM total.
>
> My questions are:
>
> 1) What would be a sensible amount of memory to specify with the '-m'
> parameter to the EAL?
> 2) What size / number of hugepages should I allocate in Linux?
>
> (I currently use boot parameters: 'hugepagesz=1G hugepages=20 hugepagesz=2M
> hugepages=0').
>
> Best regards
> David
For most DPDK applications the predominate user of huge pages is any
mbuf pools you create. You should be able to calculate the worst case size
of all rings and mbuf pools and size your huge memory from that.
next prev parent reply other threads:[~2020-12-09 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 16:34 David Aldrich
2020-12-09 16:59 ` Stephen Hemminger [this message]
2020-12-09 18:30 ` David Aldrich
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=20201209085932.60a0f9ea@hermes.local \
--to=stephen@networkplumber.org \
--cc=david.aldrich.ntml@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).