DPDK patches and discussions
 help / color / mirror / Atom feed
From: lic121 <chengtcli@qq.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>,
	"David Marchand" <david.marchand@redhat.com>, dev <dev@dpdk.org>
Subject: Re: [PATCH] eal: zero out new added memory
Date: Sat, 3 Sep 2022 13:53:26 +0000	[thread overview]
Message-ID: <tencent_475CB0B9CA3134A2D74608E8BA883DBDC408@qq.com> (raw)
In-Reply-To: <tencent_3CA2FC46CAE821885EBD935C66B965312C08@qq.com>

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.

      reply	other threads:[~2022-09-03 13:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27  9:25 chengtcli
2022-08-27  9:57 ` Dmitry Kozlyuk
2022-08-27 13:31   ` lic121
2022-08-27 14:56     ` Dmitry Kozlyuk
2022-08-29  1:18       ` lic121
2022-08-29 11:37         ` lic121
2022-08-29 11:57           ` David Marchand
2022-08-29 12:37             ` Morten Brørup
2022-08-29 12:43               ` David Marchand
2022-08-29 12:49               ` Dmitry Kozlyuk
2022-08-30  1:11                 ` lic121
2022-08-30  9:49                   ` lic121
2022-08-30 10:59                     ` Dmitry Kozlyuk
2022-08-30 12:47                       ` lic121
2022-08-30 12:53                       ` lic121
2022-09-03 13:53                         ` lic121 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tencent_475CB0B9CA3134A2D74608E8BA883DBDC408@qq.com \
    --to=chengtcli@qq.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=mb@smartsharesystems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).