All of lore.kernel.org
 help / color / mirror / Atom feed
From: john miller <john.miller@atomicrules.com>
To: dev@dpdk.org
Subject: error in testpmd when CONFIG_RTE_BUILD_SHARED_LIB=y
Date: Tue, 11 Apr 2017 14:02:40 -0400	[thread overview]
Message-ID: <357262EF-AA7B-4064-963E-FF130E4607E6@atomicrules.com> (raw)


We are seeing an issue when running from the head of the master branch in dpdk-next-net and building with CONFIG_RTE_BUILD_SHARED_LIB=y.   When we run testpmd using  -d to point to our PMD we get this error

EAL: Error - exiting with code: 1
  Cause: Creation of mbuf pool for socket 0 failed: Invalid argument

This error occurs as a result of the rte mempool ops table having 0 entries.  This table is populated from a call to rte_mempool_register_ops().  This function gets called in rte_mempool_ring.c via the static initialization MACRO MEMPOOL_REGISTER_OPS and exists in librte_mempool_ring.so.  However this library is not loaded when the rte_eal_init() gets called so the static initializers are not yet loaded.   

I am requesting advice on the proper way to repair this.

Thank you,
-John

             reply	other threads:[~2017-04-11 18:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 18:02 john miller [this message]
2017-04-11 19:28 ` error in testpmd when CONFIG_RTE_BUILD_SHARED_LIB=y Thomas Monjalon
2017-04-12  4:52   ` Shreyansh Jain
2017-04-12 10:05     ` Bruce Richardson
2017-04-12 10:25       ` Thomas Monjalon
2017-04-12 11:40         ` Neil Horman
2017-04-12 10:26       ` Shreyansh Jain
2017-04-12 10:32         ` Ananyev, Konstantin
2017-04-12 10:33         ` Shreyansh Jain
2017-04-12 10:38           ` Bruce Richardson
2017-04-12 10:42             ` Bruce Richardson
2017-04-12 11:02               ` Van Haaren, Harry
2017-04-12 11:02               ` Shreyansh Jain
2017-04-12 11:31                 ` Richardson, Bruce
2017-04-12 12:31                   ` Thomas Monjalon
2017-04-12 19:55                     ` Olivier MATZ
2017-04-13  6:41                       ` Shreyansh Jain
2017-04-13  6:53                         ` Thomas Monjalon
2017-04-12 14:43                 ` Ananyev, Konstantin

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=357262EF-AA7B-4064-963E-FF130E4607E6@atomicrules.com \
    --to=john.miller@atomicrules.com \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.