From: Stephen Hemminger <stephen@networkplumber.org>
To: IraM <iramica@yahoo.com>
Cc: users@dpdk.org
Subject: Re: How do you calculate DPDK mempool requirements?
Date: Tue, 6 Dec 2022 08:24:57 -0800 [thread overview]
Message-ID: <20221206082457.3574df15@hermes.local> (raw)
In-Reply-To: <92C51315-3CB2-47A6-9BEE-4674C7665A35@yahoo.com>
On Tue, 6 Dec 2022 07:16:13 -0500
IraM <iramica@yahoo.com> wrote:
> Sent from my iPhone
>
> > On Dec 5, 2022, at 12:39, Dylan Baros <dcbaros@utexas.edu> wrote:
> >
> >
> >
> >
> > How do you figure out what settings need to be used to correctly configure a DPDK mempool for your application?
>
> I went to rough a similar exercise when I was playing around with packet ordering example.
>
> Here’s a rough formula I came up with.
> Comments are welcomed
>
> Total pool size = Sum of the following numbers
> -RX queue size x number of ports
> -TX queue size x number of ports
> -Size of ring x number of rings
> -MAX_pkt_burstsize x number of threads since each does a read of that size
>
>
>
Some drivers like Broadcom bnxt require multiple mbufs per rx descriptor.
And if you use jumbo frames and scatter/gather it gets a little more complex.
prev parent reply other threads:[~2022-12-06 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 17:32 Dylan Baros
2022-12-05 18:28 ` Stephen Hemminger
2022-12-06 12:16 ` IraM
2022-12-06 16:24 ` Stephen Hemminger [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=20221206082457.3574df15@hermes.local \
--to=stephen@networkplumber.org \
--cc=iramica@yahoo.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).