Re: [dpdk-users] segfault with dpdk 16.07 in rte_mempool_populate_phys

[Shreyansh Jain <shreyansh.jain@nxp.com>]

Hi Martin,

(Sorry. I have converted the email to plain-text)

Happy to hear this. Probably next time I too will keep in mind the importance of init/contructor.

====
> From: martin_curran-gray@keysight.com [mailto:martin_curran-gray@keysight.com] 
> Sent: Wednesday, August 24, 2016 12:18 PM
> To: users@dpdk.org; Shreyansh Jain <shreyansh.jain@nxp.com>
> Cc: martin_curran-gray@keysight.com
> Subject: Re: [dpdk-users] segfault with dpdk 16.07 in rte_mempool_populate_phys
> 
> 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

[Shreyansh] That is a good increase.

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

[Shreyansh] I am not sure what does the above mean (vector mode) - so, no comments from my side.

>
> Thanks for your help
> Martin
[..]

-
Shreyansh