Re: [PATCH] eal: zero out new added memory

2022-09-03 Thread lic121
On Tue, Aug 30, 2022 at 12:53:37PM +, lic121 wrote: > On Tue, Aug 30, 2022 at 01:59:16PM +0300, Dmitry Kozlyuk wrote: > > Thank you for the most detailed info! > > > > 1. If you run the poisoner program the second time, > >does it also see dirty memory immediately after mmap()? > > No, ru

Re: [PATCH] eal: zero out new added memory

2022-08-30 Thread lic121
On Tue, Aug 30, 2022 at 01:59:16PM +0300, Dmitry Kozlyuk wrote: > Thank you for the most detailed info! > > 1. If you run the poisoner program the second time, >does it also see dirty memory immediately after mmap()? No, running the poisoner program again doesn't show dirty memory immediately

Re: [PATCH] eal: zero out new added memory

2022-08-30 Thread lic121
On Tue, Aug 30, 2022 at 01:59:16PM +0300, Dmitry Kozlyuk wrote: > Thank you for the most detailed info! > > 1. If you run the poisoner program the second time, >does it also see dirty memory immediately after mmap()? If I run the poisoner program the second time, no dirty memory. There could

Re: [PATCH] eal: zero out new added memory

2022-08-30 Thread Dmitry Kozlyuk
Thank you for the most detailed info! 1. If you run the poisoner program the second time, does it also see dirty memory immediately after mmap()? 2. Kernel 4.19.90-2102 patchlevel 2102 is very high, can there be any unusual patches applied? Your host has "compute" in its name, can it

Re: [PATCH] eal: zero out new added memory

2022-08-30 Thread lic121
On Tue, Aug 30, 2022 at 01:11:25AM +, lic121 wrote: > On Mon, Aug 29, 2022 at 03:49:25PM +0300, Dmitry Kozlyuk wrote: > > 2022-08-29 14:37 (UTC+0200), Morten Brørup: > > > > From: David Marchand [mailto:david.march...@redhat.com] > > > > Sent: Monday, 29 August 2022 13.58 > > > > > > > > > > >

Re: [PATCH] eal: zero out new added memory

2022-08-29 Thread lic121
On Mon, Aug 29, 2022 at 03:49:25PM +0300, Dmitry Kozlyuk wrote: > 2022-08-29 14:37 (UTC+0200), Morten Brørup: > > > From: David Marchand [mailto:david.march...@redhat.com] > > > Sent: Monday, 29 August 2022 13.58 > > > > > > > > > > On Sat, Aug 27, 2022 at 12:57:50PM +0300, Dmitry Kozlyuk wrote:

Re: [PATCH] eal: zero out new added memory

2022-08-29 Thread Dmitry Kozlyuk
2022-08-29 14:37 (UTC+0200), Morten Brørup: > > From: David Marchand [mailto:david.march...@redhat.com] > > Sent: Monday, 29 August 2022 13.58 > > > > > > > > On Sat, Aug 27, 2022 at 12:57:50PM +0300, Dmitry Kozlyuk wrote: > > > > > > > The kernel ensures that the newly mapped memory is zeroed, >

Re: [PATCH] eal: zero out new added memory

2022-08-29 Thread David Marchand
On Mon, Aug 29, 2022 at 2:37 PM Morten Brørup wrote: > > > From: David Marchand [mailto:david.march...@redhat.com] > > Sent: Monday, 29 August 2022 13.58 > > > > On Mon, Aug 29, 2022 at 1:38 PM lic121 wrote: > > > > > > On Mon, Aug 29, 2022 at 01:18:36AM +, lic121 wrote: > > > > On Sat, Aug

RE: [PATCH] eal: zero out new added memory

2022-08-29 Thread Morten Brørup
> From: David Marchand [mailto:david.march...@redhat.com] > Sent: Monday, 29 August 2022 13.58 > > On Mon, Aug 29, 2022 at 1:38 PM lic121 wrote: > > > > On Mon, Aug 29, 2022 at 01:18:36AM +, lic121 wrote: > > > On Sat, Aug 27, 2022 at 05:56:54PM +0300, Dmitry Kozlyuk wrote: > > > > 2022-08-27

Re: [PATCH] eal: zero out new added memory

2022-08-29 Thread David Marchand
On Mon, Aug 29, 2022 at 1:38 PM lic121 wrote: > > On Mon, Aug 29, 2022 at 01:18:36AM +, lic121 wrote: > > On Sat, Aug 27, 2022 at 05:56:54PM +0300, Dmitry Kozlyuk wrote: > > > 2022-08-27 13:31 (UTC+), lic121: > > > > On Sat, Aug 27, 2022 at 12:57:50PM +0300, Dmitry Kozlyuk wrote: > > > > >

Re: [PATCH] eal: zero out new added memory

2022-08-29 Thread lic121
On Mon, Aug 29, 2022 at 01:18:36AM +, lic121 wrote: > On Sat, Aug 27, 2022 at 05:56:54PM +0300, Dmitry Kozlyuk wrote: > > 2022-08-27 13:31 (UTC+), lic121: > > > On Sat, Aug 27, 2022 at 12:57:50PM +0300, Dmitry Kozlyuk wrote: > > > > 2022-08-27 09:25 (UTC+), chengt...@qq.com: > > > > >

Re: [PATCH] eal: zero out new added memory

2022-08-28 Thread lic121
On Sat, Aug 27, 2022 at 05:56:54PM +0300, Dmitry Kozlyuk wrote: > 2022-08-27 13:31 (UTC+), lic121: > > On Sat, Aug 27, 2022 at 12:57:50PM +0300, Dmitry Kozlyuk wrote: > > > 2022-08-27 09:25 (UTC+), chengt...@qq.com: > > > > From: lic121 > > > > > > > > When RTE_MALLOC_DEBUG not configur

Re: [PATCH] eal: zero out new added memory

2022-08-27 Thread Dmitry Kozlyuk
2022-08-27 13:31 (UTC+), lic121: > On Sat, Aug 27, 2022 at 12:57:50PM +0300, Dmitry Kozlyuk wrote: > > 2022-08-27 09:25 (UTC+), chengt...@qq.com: > > > From: lic121 > > > > > > When RTE_MALLOC_DEBUG not configured, rte_zmalloc_socket() doens't > > > zero oute allocaed memory. Because me

Re: [PATCH] eal: zero out new added memory

2022-08-27 Thread lic121
On Sat, Aug 27, 2022 at 12:57:50PM +0300, Dmitry Kozlyuk wrote: > 2022-08-27 09:25 (UTC+), chengt...@qq.com: > > From: lic121 > > > > When RTE_MALLOC_DEBUG not configured, rte_zmalloc_socket() doens't > > zero oute allocaed memory. Because memory are zeroed out when free > > in malloc_elem_fr

Re: [PATCH] eal: zero out new added memory

2022-08-27 Thread Dmitry Kozlyuk
2022-08-27 09:25 (UTC+), chengt...@qq.com: > From: lic121 > > When RTE_MALLOC_DEBUG not configured, rte_zmalloc_socket() doens't > zero oute allocaed memory. Because memory are zeroed out when free > in malloc_elem_free(). But seems the initial allocated memory is > not zeroed out as expected

[PATCH] eal: zero out new added memory

2022-08-27 Thread chengtcli
From: lic121 When RTE_MALLOC_DEBUG not configured, rte_zmalloc_socket() doens't zero oute allocaed memory. Because memory are zeroed out when free in malloc_elem_free(). But seems the initial allocated memory is not zeroed out as expected. This patch zero out initial allocated memory in malloc_h