DPDK usage discussions
 help / color / mirror / Atom feed
From: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: RE: How to increase mbuf size in dpdk version 17.11
Date: Tue, 1 Mar 2022 21:30:28 +0000	[thread overview]
Message-ID: <SJ0PR01MB639963B00671DFC3851E79108F029@SJ0PR01MB6399.prod.exchangelabs.com> (raw)
In-Reply-To: <20220301115638.62387935@hermes.local>

Hi Stephen,
The VM is configured to have 32 GB of memory.  
Will dpdk consume the 2GB of hugepage memory for the mbufs?  
I don't mind having less mbufs with mbuf size of 16K vs original mbuf size of 2K.

Thanks,
Ed

-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org> 
Sent: Tuesday, March 1, 2022 2:57 PM
To: Lombardo, Ed <Ed.Lombardo@netscout.com>
Cc: users@dpdk.org
Subject: Re: How to increase mbuf size in dpdk version 17.11

External Email: This message originated outside of NETSCOUT. Do not click links or open attachments unless you recognize the sender and know the content is safe.

On Tue, 1 Mar 2022 18:34:22 +0000
"Lombardo, Ed" <Ed.Lombardo@netscout.com> wrote:

> Hi,
> I have an application built with dpdk 17.11.
> During initialization I want to change the mbuf size from 2K to 16K.
> I want to receive packet sizes of 8K or more in one mbuf.
> 
> The VM running the application is configured to have 2G hugepages.
> 
> I tried many things and I get an error when a packet arrives.
> 
> I read online that there is #define DEFAULT_MBUF_DATA_SIZE that I changed from 2176 to ((2048*8)+128), where 128 is for headroom.
> The call to rte_pktmbuf_pool_create() returns success with my changes.
> From the rte_mempool_dump() - "rx_nombuf" - Total number of Rx mbuf allocation failures.  This value increments each time a packet arrives.
> 
> Is there any reference document explaining what causes this error?
> Is there a user guide I should follow to make the mbuf size change, starting with the hugepage value?
> 
> Thanks,
> Ed

Did you check that you have enough memory in the system for the larger footprint?
Using 16K per mbuf is going to cause lots of memory to be consumed.

  reply	other threads:[~2022-03-01 21:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 18:34 Lombardo, Ed
2022-03-01 19:56 ` Stephen Hemminger
2022-03-01 21:30   ` Lombardo, Ed [this message]
2022-03-01 21:37     ` Cliff Burdick
2022-03-01 22:46       ` Stephen Hemminger
2022-03-02  1:37         ` Lombardo, Ed
2022-03-02  3:45           ` Cliff Burdick
2022-03-02  3:50             ` Lombardo, Ed
2022-03-02  3:56               ` Cliff Burdick
2022-03-02  4:40                 ` Stephen Hemminger
2022-03-02  5:48                   ` Lombardo, Ed
2022-03-02 14:47                     ` Cliff Burdick
2022-03-02 14:20                 ` Lombardo, Ed

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=SJ0PR01MB639963B00671DFC3851E79108F029@SJ0PR01MB6399.prod.exchangelabs.com \
    --to=ed.lombardo@netscout.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
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).