From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6C297A034F for ; Tue, 1 Mar 2022 22:37:22 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2E4C140696; Tue, 1 Mar 2022 22:37:22 +0100 (CET) Received: from mail-ej1-f48.google.com (mail-ej1-f48.google.com [209.85.218.48]) by mails.dpdk.org (Postfix) with ESMTP id DC6A640040 for ; Tue, 1 Mar 2022 22:37:20 +0100 (CET) Received: by mail-ej1-f48.google.com with SMTP id qt6so262134ejb.11 for ; Tue, 01 Mar 2022 13:37:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=I89D7AL3q6R59kuO9AdV3Y+K6iWMv6FjR8TNaB18/gI=; b=KSGUS2TaPGHl+R/1DvN18x5IOD7Cv7ZzBTvdxtF/178N/X5RjFNpg+j/K7TreJ2ffI DTWaIqrd4SOva7By9SqP7osQ9JoYAx7pu7z27C9VrvkdPySasFltTL3SueY+z0X5qUS6 K24x7B/zyIS1UF4VQkymZD3ygV/mwm4p/SrzJTwh93EKgBNANfHkXFjeOErFj7k07XMK 1DvH1nB8pDBGJAIKAwZDGIVjcwbMVKBgv002vR5FLc983vzbT8njUJL1ike0xsCFOB+w 8bYqR53QUX5nJ7Trf+n98czOpEk65Cs3Ol/rayejfR71ptKxlpM2XXX/TshW6jNWNuzW 73xg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=I89D7AL3q6R59kuO9AdV3Y+K6iWMv6FjR8TNaB18/gI=; b=FhBg6aKawyCJO9NblAmn3rtwagTVMsuIKE796Iy+/aZSoOQ6Hv2rbAnDRMuuLU2BPx LAAl0ZIdm26HhevJP7uteIwsEkJKoJbVsidxX+7+gdrT+fbEaMZ1Le1V+4WegIy/vVkS EGTrFd5MIpxpmfE89B/9+nsKWC2QfiQp8xKWMgZ8xK1++SpO+cJryfmVwLpLt/a70KvY QDq/q/hf5ocEfJzP6pJFCBm3taD68Wo31ttYx9Sp7CLWVuRIg0aycRIoOVTMyxbHZeNZ 3vo96egvtChhj+SxiZWYk78yQvo5XpDiwJVpd8iQ8GBRe8H1O5tE3XfYKtHoIL9Py6bi nRNA== X-Gm-Message-State: AOAM532Fdz2YOSqgZy2zrNyebhCXO0Jj3AmGiIleRulegeI5VTXiB93I 5YeAFIcb4DE6rurB8Ipv+pE8Mfz2ulDQfadPVuUQCd5D X-Google-Smtp-Source: ABdhPJwTDq4CrE0I6oZMYK0j1XDvw1l+p3ZIcc6XKwalGtWFjaP25eczh5YokAGHNByNEMv49Jh4GTV1OyjZYbAvcO8= X-Received: by 2002:a17:907:a088:b0:6d6:f8f9:b15a with SMTP id hu8-20020a170907a08800b006d6f8f9b15amr2914210ejc.203.1646170640300; Tue, 01 Mar 2022 13:37:20 -0800 (PST) MIME-Version: 1.0 References: <20220301115638.62387935@hermes.local> In-Reply-To: From: Cliff Burdick Date: Tue, 1 Mar 2022 13:37:07 -0800 Message-ID: Subject: Re: How to increase mbuf size in dpdk version 17.11 To: "Lombardo, Ed" Cc: Stephen Hemminger , "users@dpdk.org" Content-Type: multipart/alternative; boundary="000000000000413c7f05d92ef8a3" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --000000000000413c7f05d92ef8a3 Content-Type: text/plain; charset="UTF-8" Can you verify how many buffers you're allocating? I don't see how many you're allocating in this thread. On Tue, Mar 1, 2022 at 1:30 PM Lombardo, Ed wrote: > 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 > Sent: Tuesday, March 1, 2022 2:57 PM > To: Lombardo, Ed > 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" 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. > --000000000000413c7f05d92ef8a3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Can you verify how many buffers you'r= e allocating? I don't see how many you're allocating in this thread= .

On Tue, Mar 1, 2022 at 1:30 PM Lombardo, Ed <Ed.Lombardo@netscout.com> wrote:
Hi Stephen,
The VM is configured to have 32 GB of memory.=C2=A0
Will dpdk consume the 2GB of hugepage memory for the mbufs?=C2=A0
I don't mind having less mbufs with mbuf size of 16K vs original mbuf s= ize 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<= br> Subject: Re: How to increase mbuf size in dpdk version 17.11

External Email: This message originated outside of NETSCOUT. Do not click l= inks or open attachments unless you recognize the sender and know the conte= nt 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 chan= ged 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.=C2=A0 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, st= arting with the hugepage value?
>
> Thanks,
> Ed

Did you check that you have enough memory in the system for the larger foot= print?
Using 16K per mbuf is going to cause lots of memory to be consumed.
--000000000000413c7f05d92ef8a3--