From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 4389EA0543;
	Sat,  3 Sep 2022 15:53:40 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id DF7BB40A7F;
	Sat,  3 Sep 2022 15:53:39 +0200 (CEST)
Received: from out203-205-221-221.mail.qq.com (out203-205-221-221.mail.qq.com
 [203.205.221.221])
 by mails.dpdk.org (Postfix) with ESMTP id B78C040698
 for <dev@dpdk.org>; Sat,  3 Sep 2022 15:53:37 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qq.com; s=s201512;
 t=1662213213; bh=dXIuT7jnDhAoxO3jUOusachnCQ2Q4Tsp8YlgcFB8pdc=;
 h=Date:From:To:Cc:Subject:References:In-Reply-To;
 b=AEXNi7KGz6NQBT516OyVjYJROIVJTcJoC8P/rqYS3QTJ0jnyIE4oAYL0V/7fyqfLQ
 zZ4VCvuKYOrhc1/X+NwKp9UzU/ckEzCRO/sLrA3GZd02cK0Ymjdly+w1gCGGnet9u2
 37PAk3h0ALU0E3EWPsA1bbARwT08plmVQP2auhAY=
Received: from vscode.7~ ([222.210.155.225])
 by newxmesmtplogicsvrsza5.qq.com (NewEsmtp) with SMTP
 id D5A3D6A4; Sat, 03 Sep 2022 21:53:26 +0800
X-QQ-mid: xmsmtpt1662213206tnn5jua6f
Message-ID: <tencent_475CB0B9CA3134A2D74608E8BA883DBDC408@qq.com>
X-QQ-XMAILINFO: MiPTq5wGoKOmkEBsKlLfIat0TZP4dNEdZnH9dRnPFqJoZ42Hbg6xtUWkV8fJKZ
 43CXC0BQMTXJs/ZV4dMUXt4261+ScD/QUF1wQm8gIKE1Oh8U6zMsYeUx/zhKYR5m+LBO+1Ra7NUq
 CVV4oeYm2v/QYB4GSMnHguGRuNM8iPufuNujS3GbiyQ64+KJd7SuL+SvHe/ZzCsCt6ReNVoEtWGN
 Y6NUVaMOibV7BzY620gEJZfi1XQETHq9faUShyMfyfpJ0KwaevYw9za+CO2b/l4J05ot4/8KxMIt
 NJ7ed1IX08KeMpmyeFv39XMR5GIifIOAsu88aMNv/2SMHgYfOk8flHNAZldeuJWNGJJOWy6zFpr9
 73HudntGWrbSwLm1oR3ycpchLJqMHceABDb2TP454PNDKh32jv5Fp2URQKBTjieI762m0dJCiAVG
 PFrVlvosV4Y3PAGl9gN8Aa83kYpevGT30ArzfR0rOvky0bgBxdi5MDPtnzmXsqRXMd2mdj8wkLrH
 Cf5HRZQWq/rNl6vz+A/iDsP5Ae5+CnxyeU/aaQt7y2dJ+mWt7Zr5Dn4VvxCSuYYyp8qMl+lVxj92
 BOhKmeTNXc6WELzlKz2HS5BcupGueQHVNvVu1b00z5DkbC9lEomER/VUoCJQZ6yjyKZbh2SWeaP7
 9mzXa2c1WaElVjX5jybabcnXb7mRbFTRRWLtfYleKptJRJg28wGbgb1AXXlaMo7qUhMgUWMzC+Tn
 yChiRZ9RPVHXNYrOn9YgwhmpebZlzay0kuXMaAT9+0owUtR2RYBFVr1bi78YlYd3VrjQ8KaUyMk1
 Kibdb3gicjjFrTxKVNfvkKGtEju3MQxCpsxmhN4V4YIjhvRHBA+A4qYm2SEMCMKOEHxRnRCtclVK
 tFFbz/WbU7Egtp3HYehxuJI4qXuO792/24wCPyYXtzGztZ+DRzinM50KPEzVxqgXVk5Qts4xw3KD
 FjT7gjLybIFWDWpguor5z+GQYBo9yhEzhUzNND+AT7FX+KNdjHZcTcbozzkiLN
Date: Sat, 3 Sep 2022 13:53:26 +0000
From: lic121 <chengtcli@qq.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: Morten =?iso-8859-1?Q?Br=F8rup?= <mb@smartsharesystems.com>,
 David Marchand <david.marchand@redhat.com>, dev <dev@dpdk.org>
Subject: Re: [PATCH] eal: zero out new added memory
X-OQ-MSGID: <20220903135326.GA19734@vscode.7~>
References: <20220827175654.7a167eaf@sovereign>
 <tencent_9CA2824675E850887CBDAA5C76B94131A908@qq.com>
 <tencent_93CEF4C2700DE476C4A48B3A1BD1A21F210A@qq.com>
 <CAJFAV8x8c7xth4WmXPG3bautS43YBS3OKfDmKekozW1U=ri+jg@mail.gmail.com>
 <98CBD80474FA8B44BF855DF32C47DC35D872CC@smartserver.smartshare.dk>
 <20220829154925.6575540a@sovereign>
 <tencent_1386F7B27341E526C40C8A6A1B45A077200A@qq.com>
 <tencent_8797502E4A0CA9E8A25108FA096244AF1306@qq.com>
 <20220830135916.12c5e836@sovereign>
 <tencent_3CA2FC46CAE821885EBD935C66B965312C08@qq.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <tencent_3CA2FC46CAE821885EBD935C66B965312C08@qq.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

On Tue, Aug 30, 2022 at 12:53:37PM +0000, 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, running the poisoner program again doesn't show dirty memory
> immediately after mmap.
> 
> I assume that there are some differences on how my poisoner program
> using hugepage and how testpmd using hugepage. I notice that testpmd
> leaves some files under /dev/hugepages/rtemap_xxx even after testpmd
> process exits. But my program didn't create any file under
> /dev/hugepages/.
> > 
> > 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 have patches that trade security for performance?
> 
> I may need to talk to the kernel team. Indeed, I failed to reproduce the
> issue on a Virtual Machine of kernel 4.18.0-305.12.1.el8_4.x86_64.(2M
> page size insetad of 1G)

Verified that this issue is caused by an down stream linux kernel issue.
Thanks for your attention.