DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Aldrich <david.aldrich.ntml@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] 'MBUF: error setting mempool handler'
Date: Thu, 4 Jun 2020 10:23:19 -0700	[thread overview]
Message-ID: <20200604102319.146abf16@hermes.lan> (raw)
In-Reply-To: <CAJK_iegDrOhUz6ct4RyqTV4SP0-n9-tVo2ypqA_andSPPJj7vw@mail.gmail.com>

On Thu, 4 Jun 2020 17:50:18 +0100
David Aldrich <david.aldrich.ntml@gmail.com> wrote:

> I am using some DPDK application code that worked with DPDK 2.2.0.  I am
> trying to port it to DPDK 18.08.  The code gives error:
> 
> MBUF: error setting mempool handler
> 
> 
> I guess the app code that causes this is:
> 
> ptRxQueInfo->pool = rte_mempool_create(buf,
> >                                nb_mbuf/2,
> >                                MBUF_SIZE,
> >                                0,
> >                                sizeof(struct rte_pktmbuf_pool_private),
> >
> >                                rte_pktmbuf_pool_init,
> >                                NULL,
> >                                rte_pktmbuf_init,
> >                                NULL,
> >                                iCpuSocket,
> >                                0)  
> 
> 
> I really don't know how to fix this. Any suggestions please?

You should not be using 8.08 is not a Long Term Stable release. It is not supported.

You should be using rte_pktmbuf_pool_create() rather than rte_mempool_create().
Lots has changed in the years since 2.2.0


  reply	other threads:[~2020-06-04 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 16:50 David Aldrich
2020-06-04 17:23 ` Stephen Hemminger [this message]
2020-06-05  9:43   ` David Aldrich
2020-06-05 16:20     ` David Aldrich
2020-06-18 10:18       ` Kevin Traynor

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=20200604102319.146abf16@hermes.lan \
    --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).