DPDK usage discussions
 help / color / mirror / Atom feed
From: David Aldrich <david.aldrich.ntml@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Basic hugepages question
Date: Wed, 9 Dec 2020 18:30:26 +0000
Message-ID: <CAJK_ieiPe+CzSqZwVYR35+cbgvy4_kdF9RW4g1vP9zALeH1emA@mail.gmail.com> (raw)
In-Reply-To: <20201209085932.60a0f9ea@hermes.local>

Thank you for your reply. I estimate the mbuf pools to be ~150MB. So would
a sensible hugepages configuration be 100 pages of 2MB each?


On Wed, Dec 9, 2020 at 5:00 PM Stephen Hemminger <stephen@networkplumber.org>
wrote:

> 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.
>

      reply	other threads:[~2020-12-09 18:30 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
2020-12-09 18:30   ` David Aldrich [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=CAJK_ieiPe+CzSqZwVYR35+cbgvy4_kdF9RW4g1vP9zALeH1emA@mail.gmail.com \
    --to=david.aldrich.ntml@gmail.com \
    --cc=stephen@networkplumber.org \
    --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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git