From: Olivier Matz <olivier.matz@6wind.com>
To: "Wiles, Keith" <keith.wiles@intel.com>,
Keren Hochman <keren.hochman@lightcyber.com>
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] disable hugepages
Date: Thu, 10 Nov 2016 14:34:23 +0100 [thread overview]
Message-ID: <0fa3b042-bb5f-04f9-5ac4-bb70c8765340@6wind.com> (raw)
In-Reply-To: <6BBBABF1-45E1-4260-BE26-9C556C47B825@intel.com>
On 11/10/2016 02:10 PM, Wiles, Keith wrote:
>
>> On Nov 10, 2016, at 6:32 AM, Keren Hochman <keren.hochman@lightcyber.com> wrote:
>>
>> I tried using the following dpdk options:
>> --no-huge --vdev eth_pcap0 ,rx_pcap=/t1,tx_pcap=/t2
>> *It's worked but the number of elements is limited, although the machine
>> has enough free memory. *rte_mempool_create is failed when I'm trying to
>> allocate more memory. Is there any limitation on the memory beside the
>> machine?
>
> DPDK will just use the standard linux memory allocator, so no limitation in DPDK. Now you could be hitting the limit as a user, need to check your system to make sure you can allocate that much memory to a user. Try using the command ulimit and see what it reports.
>
> I do not remember exactly how to change limits except with ulimit command. I may have modified /etc/security/limits.conf file.
I don't think it's a ulimit issue.
Actually, the memory is reserved once at startup. The -m EAL
option allows to specify the amount of memory allocated:
-m MB Memory to allocate (see also --socket-mem)
So I guess setting it to an higher value (256?) would do the job.
Regards,
Olivier
prev parent reply other threads:[~2016-11-10 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 12:55 Keren Hochman
2016-11-09 13:40 ` Christian Ehrhardt
2016-11-09 14:40 ` Keren Hochman
2016-11-09 14:50 ` Olivier Matz
2016-11-10 12:32 ` Keren Hochman
2016-11-10 13:10 ` Wiles, Keith
2016-11-10 13:34 ` Olivier Matz [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=0fa3b042-bb5f-04f9-5ac4-bb70c8765340@6wind.com \
--to=olivier.matz@6wind.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=keren.hochman@lightcyber.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).