DPDK patches and discussions
 help / color / mirror / Atom feed
From: Feng Li <lifeng1519@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Li Feng <fengli@smartx.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	 Kyle Zhang <kyle@smartx.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: add madvise to avoid dump memory
Date: Mon, 20 Apr 2020 17:40:37 +0800	[thread overview]
Message-ID: <CAEK8JBCbvokfRYEmAhQM6VHqaAncESgu4kpewMqyYPqB9aT39A@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8yZ2KvS7y1v9jgVhfwOrfpFUvPBgEBmfUqQXdaX49CAoA@mail.gmail.com>

Thank you, Marchand,

I have just tested your patch, and it doesn't work.
The core dump file is still very very large, the same to virtual memory size.

David Marchand <david.marchand@redhat.com> 于2020年4月20日周一 下午3:13写道：
>
> On Mon, Apr 20, 2020 at 9:10 AM Li Feng <fengli@smartx.com> wrote:
> > Li Feng <fengli@smartx.com> 于2020年4月20日周一 下午3:04写道：
> > >
> > > Avoid dump all mmapped memory to coredump file when crash.
> > > Otherwise it will very large and it's hard to analyze with gdb.
> > >
> > > In my test, it will dump 128GiB memory to coredump file when integrated
> > > to spdk with default configuration.
>
> Can you test with current master which has this change?
> https://git.dpdk.org/dpdk/commit?id=8a4baf06c17a806696fb10aba36fce7471983028
>
> Thanks.
>
> --
> David Marchand
>

  reply	other threads:[~2020-04-20 15:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200420070508.645533-1-fengli@smartx.com>
2020-04-20  7:07 ` Li Feng
2020-04-20  7:13   ` David Marchand
2020-04-20  9:40     ` Feng Li [this message]
2020-04-21  7:41       ` David Marchand
2020-04-21 11:06         ` Feng Li
2020-04-21 12:19           ` Burakov, Anatoly
2020-04-21 16:38             ` Feng Li
2020-04-21 17:02               ` Burakov, Anatoly
2020-04-22  3:13                 ` Li Feng
2020-04-22  9:53                   ` Burakov, Anatoly
     [not found]                     ` <CAEK8JBCdfZJiKNjDNgC9nDGLni9Dvw+U1doRFnh+zkAs5TXEsg@mail.gmail.com>
2020-04-23 12:22                       ` Burakov, Anatoly
2020-04-23 15:43 ` [dpdk-dev] [PATCH v2] " Li Feng
2020-04-23 16:33   ` Burakov, Anatoly
2020-04-23 20:04     ` David Marchand
2020-04-24  9:12       ` Burakov, Anatoly
2020-04-24  9:14         ` Bruce Richardson
2020-04-24  9:33           ` Feng Li
2020-04-24 11:00             ` Burakov, Anatoly
2020-04-24 12:03               ` Li Feng

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=CAEK8JBCbvokfRYEmAhQM6VHqaAncESgu4kpewMqyYPqB9aT39A@mail.gmail.com \
    --to=lifeng1519@gmail.com \
    --cc=anatoly.burakov@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=fengli@smartx.com \
    --cc=kyle@smartx.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).