DPDK patches and discussions
 help / color / mirror / Atom feed
From: Li Feng <fengli@smartx.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Feng Li <lifeng1519@gmail.com>,
	David Marchand <david.marchand@redhat.com>,
	Kyle Zhang <kyle@smartx.com>, dev <dev@dpdk.org>,
	Yang Fan <fanyang@smartx.com>
Subject: Re: [dpdk-dev] [PATCH] eal: add madvise to avoid dump memory
Date: Wed, 22 Apr 2020 11:13:29 +0800	[thread overview]
Message-ID: <CAHckoCxeK9O7zv-fBC--0Twt_-9wZ6KxnLUPjV8mc4va_Q_zBA@mail.gmail.com> (raw)
In-Reply-To: <4d2145b0-91bd-23a9-d1f0-26b60585b003@intel.com>

Really？So weird.
I have tested on 4 machines, running CentOS 7.
The core dump size is the same as the first argument GiB.

Thanks,

Feng Li

Burakov, Anatoly <anatoly.burakov@intel.com> 于2020年4月22日周三 上午1:02写道：
>
> On 21-Apr-20 5:38 PM, Feng Li wrote:
> > Hi Anatoly,
> >
> > This program could run like this:
> > gcc test_map.c
> > ./a.out 2 &
> > gcore `pidof a.out`
> >
> > You will get a core dump sized to 2GiB.
> >
> > Thanks,
> > Feng Li
> >
>
> I did just that, and my core dump was ~100K in size. Hence my asking
> about any special configuration required.
>
> --
> Thanks,
> Anatoly

-- 
The SmartX email address is only for business purpose. Any sent message 
that is not related to the business is not authorized or permitted by 
SmartX.
本邮箱为北京志凌海纳科技有限公司（SmartX）工作邮箱. 如本邮箱发出的邮件与工作无关,该邮件未得到本公司任何的明示或默示的授权.



  reply	other threads:[~2020-04-22  3:13 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
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 [this message]
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=CAHckoCxeK9O7zv-fBC--0Twt_-9wZ6KxnLUPjV8mc4va_Q_zBA@mail.gmail.com \
    --to=fengli@smartx.com \
    --cc=anatoly.burakov@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=fanyang@smartx.com \
    --cc=kyle@smartx.com \
    --cc=lifeng1519@gmail.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).