From: Raslan Darawsheh <rasland@nvidia.com>
To: dpdk-dev <dev@dpdk.org>, "jerinj@marvell.com" <jerinj@marvell.com>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>,
Ali Alnubani <alialnu@nvidia.com>
Subject: DPDK Compilation consuming too much memory
Date: Wed, 15 Jun 2022 08:03:28 +0000 [thread overview]
Message-ID: <BYAPR12MB307825B38072989CE8C63571CFAD9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
Hi,
I've been facing an issue while building DPDK (mostly noticeable when building cross compilation on arm64) as follows:
meson --werror --buildtype=debugoptimized --cross-file config/arm/arm64_armv8_linux_gcc -Dexamples=all /tmp/build-aarch64-gcc;
ninja -C /tmp/build-aarch64-gcc/
I can see the memory footprint for it is around 52G which basically took all my system memory.
It happens when linking CNXK drivers.
Kindest regards,
Raslan Darawsheh
[-- Attachment #2: Type: text/html, Size: 2379 bytes --]
reply other threads:[~2022-06-15 8:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BYAPR12MB307825B38072989CE8C63571CFAD9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=alialnu@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=thomas@monjalon.net \
/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).