Hi Avinash,
For me it turned out to be a bug with duplicate detection code rather than
with DPDK. The sequence numbers were wrapping over and I didn't have enough
random bits for the payload either.
- Lavanya
On Thu, Aug 11, 2016 at 4:53 PM Yeddula, Avinash wrote:
> Hi All,
> I do have a simil
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]
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.
==
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()?
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 mem
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
6 matches
Mail list logo
