From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Ravi1.Kumar@amd.com
Subject: Re: [dpdk-dev] [PATCH] config: reduce memory requirements for DPDK
Date: Tue, 24 Jul 2018 12:04:39 +0100 [thread overview]
Message-ID: <fcbe6554-10f0-96ec-6003-fdaf78e09b2d@intel.com> (raw)
In-Reply-To: <7333019.QUcIvQh70r@xps>
On 24-Jul-18 11:23 AM, Thomas Monjalon wrote:
> 24/07/2018 12:03, Anatoly Burakov:
>> It has been reported that current memory limitations do not work
>> well on an 8-socket machines in default configuration when big
>> page sizes are used [1].
>>
>> Fix it by reducing memory amount reserved by DPDK by default to
>> 32G per page size per NUMA node. This translates to allowing us
>> to reserve 32G per page size per NUMA node on 8 nodes with 2
>> page sizes.
>>
>> [1] https://mails.dpdk.org/archives/dev/2018-July/108071.html
>>
>> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
>> ---
>>
>> Notes:
>> We could have increased CONFIG_RTE_MAX_MEM_MB but this would've
>> brought other potential problems due to increased memory
>> preallocation, and secondary process initialization is flaky
>> enough as it is. I am willing to bet that 32G per page size is
>> more than enough for the majority of use cases, and any
>> application with bigger requirements could adjust config options
>> itself.
> [...]
>> -CONFIG_RTE_MAX_MEMSEG_PER_TYPE=32768
>> -CONFIG_RTE_MAX_MEM_MB_PER_TYPE=131072
>> +CONFIG_RTE_MAX_MEMSEG_PER_TYPE=16384
>> +CONFIG_RTE_MAX_MEM_MB_PER_TYPE=32768
>
> Ideally, it should be a run-time option.
>
It can be, yes, and this can be worked on for next release. However, we
also need to have good default values that work across all supported
platforms.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-07-24 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 10:03 Anatoly Burakov
2018-07-24 10:23 ` Thomas Monjalon
2018-07-24 11:04 ` Burakov, Anatoly [this message]
2018-07-24 12:03 ` Thomas Monjalon
2018-07-25 17:43 ` Kevin Traynor
2018-07-26 9:51 ` 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=fcbe6554-10f0-96ec-6003-fdaf78e09b2d@intel.com \
--to=anatoly.burakov@intel.com \
--cc=Ravi1.Kumar@amd.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).