From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Gagandeep Singh <G.Singh@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Nipun Gupta <nipun.gupta@nxp.com>
Subject: Re: [dpdk-dev] Query regarding EAL -m option
Date: Fri, 6 Aug 2021 22:05:17 +0300 [thread overview]
Message-ID: <20210806220517.465e61b3@sovereign> (raw)
In-Reply-To: <VI1PR04MB69602FAE4045BB5C78334E62E1F39@VI1PR04MB6960.eurprd04.prod.outlook.com>
2021-08-06 09:06 (UTC+0000), Gagandeep Singh:
> Hi,
>
> I can understand "-m" option can be used in "-legacy-mode" to limit the memory reservation during the eal_init.
> Is it true for dynamic memory allocation mode as well that dynamically allocated memory cannot be more than memory specified in "-m"? Or this option is valid only for legacy mode?
>
> Regards,
> Gagab
Hi Gagab,
In any mode -m specifies how much memory to request from the OS during EAL
startup. In legacy mode, this will be the maximum amount of memory DPDK can
allocate. In dynamic mode, this is just initial amount that also will never
be freed back to the system (while everything above this will).
prev parent reply other threads:[~2021-08-06 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 9:06 Gagandeep Singh
2021-08-06 19:05 ` Dmitry Kozlyuk [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=20210806220517.465e61b3@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=G.Singh@nxp.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=nipun.gupta@nxp.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).