1. The debugging log in current DPDK RTE_MALLOC_DEBUG mode is insufficient,
which makes it difficult to locate the issues, such as:
a) When a memeory overlflow occur in rte_free, there is a little log
information. Even if abort here, we can find which API is core
dumped but we sti
On Fri, 25 Dec 2020 07:20:57 +
"Peng, ZhihongX" wrote:
> The performance of our simple scheme is better than asan. We are trying the
> asan solution.
>
> Regards,
> Peng,Zhihong
Closing this RFC, not much has changed after 5 years.
Your solution adds locking and only catches small overrun
urday, December 19, 2020 2:54 AM
To: Peng, ZhihongX
Cc: Wang, Haiyue ; Zhang, Qi Z ;
Xing, Beilei ; dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] mem_debug add more log
On Fri, 18 Dec 2020 14:21:09 -0500
Peng Zhihong wrote:
> 1. The debugging log in current DPDK RTE_MALLOC_DEBUG mode is insu
gt;
> Regards,
> Peng,Zhihong
>
> -Original Message-
> From: Stephen Hemminger
> Sent: Saturday, December 19, 2020 2:54 AM
> To: Peng, ZhihongX
> Cc: Wang, Haiyue ; Zhang, Qi Z ;
> Xing, Beilei ; dev@dpdk.org
> Subject: Re: [dpdk-dev] [RFC] mem_debug
, Xueqin
; Yu, PingX
Subject: Re: [dpdk-dev] [RFC] mem_debug add more log
On Mon, 21 Dec 2020 07:35:10 +
"Peng, ZhihongX" wrote:
> 1. I think this implement doesn't add significant overhead. Overhead only
> will be occurred in rte_malloc and rte_free.
>
>
On Fri, 18 Dec 2020 14:21:09 -0500
Peng Zhihong wrote:
> 1. The debugging log in current DPDK RTE_MALLOC_DEBUG mode is insufficient,
>which makes it difficult to locate the issues, such as:
>a) When a memeory overlflow occur in rte_free, there is a little log
> information. Even if
6 matches
Mail list logo
