From: David Marchand <david.marchand@redhat.com>
To: siddarth rai <siddsr@gmail.com>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Big spike in DPDK VSZ
Date: Tue, 10 Mar 2020 16:26:17 +0100 [thread overview]
Message-ID: <CAJFAV8wbR943B0wG-_yR9eSV+=rLKhsVVfUcy5OSjLk=5fgzvQ@mail.gmail.com> (raw)
In-Reply-To: <CAGxAMwAWPX0UHcomsvsuQek9HGFxiCqOezdwhJ4=vnOwjpPgLQ@mail.gmail.com>
On Thu, Jan 30, 2020 at 11:48 AM siddarth rai <siddsr@gmail.com> wrote:
> I did some further experiments and found out that version 18.02.2 doesn't have the problem, but the 18.05.1 release has it.
>
> Would really appreciate if someone can help, if there is a patch to get over this issue in the DPDK code ?
> This is becoming a huge practical issue for me as on multi NUMA setup, the VSZ goes above 400G and I can't get core files to debug crashes in my app.
Wrt coredumps, could you try this patch ?
http://patchwork.dpdk.org/patch/66469/
--
David Marchand
next prev parent reply other threads:[~2020-03-10 15:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 7:48 siddarth rai
2020-01-30 8:51 ` David Marchand
2020-01-30 10:47 ` siddarth rai
2020-01-30 13:15 ` Meunier, Julien (Nokia - FR/Paris-Saclay)
2020-01-31 12:14 ` siddarth rai
2020-03-10 15:26 ` David Marchand [this message]
2020-02-04 10:23 ` Burakov, Anatoly
2020-02-04 10:55 ` siddarth rai
2020-02-04 11:13 ` Burakov, Anatoly
2020-02-04 11:57 ` siddarth rai
2020-02-04 12:07 ` siddarth rai
2020-02-04 16:18 ` Burakov, Anatoly
2020-02-11 8:11 ` David Marchand
2020-02-11 10:28 ` Burakov, Anatoly
2020-02-02 9:22 ` David Marchand
2020-02-04 10:20 ` Burakov, Anatoly
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='CAJFAV8wbR943B0wG-_yR9eSV+=rLKhsVVfUcy5OSjLk=5fgzvQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=siddsr@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).