From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] eal: warn on legacy memory allocation requirement
Date: Wed, 31 Jul 2019 10:15:04 +0100 [thread overview]
Message-ID: <0a1c656a-9197-2060-5a28-f0fc72265651@intel.com> (raw)
In-Reply-To: <20190730172153.29008-1-thomas@monjalon.net>
On 30-Jul-19 6:21 PM, Thomas Monjalon wrote:
> When using --no-huge mode, dynamic allocation is not supported.
> Because of this limitation, the option --legacy-mem is implied
> and -m may be needed to specify the amount of memory to allocate.
> Otherwise the default amount MEMSIZE_IF_NO_HUGE_PAGE will be allocated.
>
> The option --socket-mem can also be used with --legacy-mem
> when hugepages are supported.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> v3:
> - replace "allocation" with "amount of reserved memory"
> - add --socket-mem
> - more rewording
> v2:
> - user-oriented message
> - trigger warning on any legacy mem option
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-07-31 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 9:34 [dpdk-dev] [PATCH] eal: warn on --no-huge " Thomas Monjalon
2019-07-18 10:18 ` Burakov, Anatoly
2019-07-18 10:29 ` Thomas Monjalon
2019-07-18 10:37 ` Burakov, Anatoly
2019-07-22 16:55 ` [dpdk-dev] [PATCH v2] eal: warn on legacy memory " Thomas Monjalon
2019-07-22 17:03 ` Thomas Monjalon
2019-07-23 9:10 ` Burakov, Anatoly
2019-07-30 17:21 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2019-07-31 9:15 ` Burakov, Anatoly [this message]
2019-08-05 9:46 ` Thomas Monjalon
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=0a1c656a-9197-2060-5a28-f0fc72265651@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--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).