[dpdk-dev] rte_eth_rx bug? duplicate message bufs

2016-08-11 Thread Yeddula, Avinash
Hi All, I do have a similar issue, any response to the below email might help me as well. Thanks -Avinash -Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Lavanya Jose Sent: Monday, August 08, 2016 11:44 AM To: users at dpdk.org; dev at dpdk.org Subject:

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

2016-08-11 Thread Chao Zhu
Gowrishankar, Thanks for the detail. If my understanding is correct, Power8 has different chips. Some of the OpenPOWER chips have 8 cores per socket. And the max threads per core is 8. Should we support this in cpu_core_map_init()? Here's a dump from the OpenPOWER system.

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

2016-08-11 Thread gowrishankar muthukrishnan
On Thursday 11 August 2016 03:59 PM, Chao Zhu wrote: > Gowrishankar, > > Thanks for the detail. > If my understanding is correct, Power8 has different chips. Some of the > OpenPOWER chips have 8 cores per socket. And the max threads per core is 8. > Should we support this in cpu_core_map_init()?

[dpdk-dev] [dpdk-users] rte_zmalloc() returning non-zeroed memory on FreeBSD

2016-08-11 Thread Thomas Monjalon
Hi, 2016-08-10 23:30, Verkamp, Daniel: > It seems that with DPDK 16.07, rte_zmalloc() and related functions no > longer return zeroed memory reliably on FreeBSD. > > I notice that commit b78c9175118f7d61022ddc5c62ce54a1bd73cea5 ("mem: do > not zero out memory on zmalloc") removed the explicit

[dpdk-dev] [PATCH] mk:fix second compile error

2016-08-11 Thread Xu, HuilongX
Hi Thomas, Could you give me some comments about this patch. Thanks a lot > -Original Message- > From: Xu, HuilongX > Sent: Tuesday, August 09, 2016 2:02 PM > To: dev at dpdk.org > Cc: Xu, HuilongX > Subject: [dpdk-dev][PATCH] mk:fix second compile error > > when compile different targets