DPDK usage discussions
 help / color / mirror / Atom feed
From: <martin_curran-gray@keysight.com>
To: <users@dpdk.org>, <shreyansh.jain@nxp.com>
Cc: <martin_curran-gray@keysight.com>
Subject: Re: [dpdk-users] segfault with dpdk 16.07 in rte_mempool_populate_phys
Date: Wed, 24 Aug 2016 06:48:28 +0000	[thread overview]
Message-ID: <22C95CA62CBADB498D32A348F0F073BC20AE2DB0@wcosexch02k.cos.is.keysight.com> (raw)

Hi Shreyansh

Found my problem, because of the way the dpdk is integrated into our sw as a prebuilt library, we don't get the automatic initialisation of objects the way I think the dpdk examples benefit from.
I'd forgotten this, we have explicit calls to things like

devinitfn_rte_i40e_driver();

so after I added an explicit call to

mp_hdlr_init_ops_mp_mc();

my function pointer deep down below  rte_mempool_create is now valid.

Seem to have a nice performance improvement of about 40% in the rate my app can handle at the front door compared to 2.2.0

Nice

Now I just need to find out why when I turn on vector mode, I never get any mbuffs returned to the pool :)

Thanks for your help

Martin



Martin Curran-Gray
HW/FPGA/SW Engineer
Keysight Technologies UK Ltd

             reply	other threads:[~2016-08-24  6:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24  6:48 martin_curran-gray [this message]
2016-08-24  7:23 ` Shreyansh Jain
  -- strict thread matches above, loose matches on Subject: below --
2016-08-17 15:03 martin_curran-gray
2016-08-19  6:10 ` Shreyansh Jain
2016-08-19  8:28   ` martin_curran-gray
2016-08-22 13:58     ` Shreyansh Jain
2016-08-22 14:06       ` martin_curran-gray

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=22C95CA62CBADB498D32A348F0F073BC20AE2DB0@wcosexch02k.cos.is.keysight.com \
    --to=martin_curran-gray@keysight.com \
    --cc=shreyansh.jain@nxp.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).