DPDK usage discussions
 help / color / mirror / Atom feed
From: Ming Fu <Ming.Fu@esentire.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] How rte_mempool_ops_table is populated in a DPDK client application?
Date: Fri, 1 Sep 2017 13:36:12 +0000	[thread overview]
Message-ID: <af6cbe8deedf4525b22d6dbbf5eefe54@mbx01cmb01p.esentire.local> (raw)

Try to make snort to receive packet from a dpdk ring as an client application. The DPDK is compiled into the snort DAQ lib statically. The DAQ lib is then linked to snort statically.

What I am find is that the rte_mempool_ops_table is all 0, causing the client to crash when free the received mbuf from the ring. I was wondering how this rte_mempool_ops_table is populated during DPDK initialization for a client application.

The my dpdk snort went through rte_eal_init(), rte_ring_lookup() and rte_mempool_lookup() without error.

Thanks
Ming

             reply	other threads:[~2017-09-01 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 13:36 Ming Fu [this message]
2017-09-01 20:26 Ming Fu
2017-09-01 20:47 ` Stephen Hemminger
2017-09-01 20:56   ` Ming Fu
2017-09-01 21:01     ` Stephen Hemminger

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=af6cbe8deedf4525b22d6dbbf5eefe54@mbx01cmb01p.esentire.local \
    --to=ming.fu@esentire.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).