[dpdk-dev] Random mbuf corruption

[Stefan Baranoff]

Thanks, all!

We have alloc/free counters in place but I'll enable those debug options.
I'll try older releases of RHEL and get back to you.

I've also eradicated pthreads in this code but also have the mempool cache
size set to 0 just in case. I should mention we hold onto mbufs for a while
(up to 30s) and have many of them available (~8GB worth at 2K per).

The entire app is fairly short (2k-3k lines) so it's not too hard to
review. We'll take another look for buffer overruns.

Thanks,
Stefan

Sent from my smart phone; people don't make typos, Swype does!
On Jun 24, 2014 7:02 AM, "Olivier MATZ" <olivier.matz at 6wind.com> wrote:

> Hi,
>
> On 06/24/2014 12:48 PM, Neil Horman wrote:
>
>> Sounds like it might be time to add in some poisoning options to the mbuf
>> allocator.
>>
>
> Such option already exists: CONFIG_RTE_LIBRTE_MBUF_DEBUG and
> RTE_LIBRTE_MEMPOOL_DEBUG will enable some runtime checks, at least
> double free and buffer overflows.
>
> Olivier
>
>