DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Keren Hochman <keren.hochman@lightcyber.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] disable hugepages
Date: Thu, 10 Nov 2016 13:10:30 +0000	[thread overview]
Message-ID: <6BBBABF1-45E1-4260-BE26-9C556C47B825@intel.com> (raw)
In-Reply-To: <CAJq3SQ77Ty-OjuCi-dk6kcFYYG-iJaFrxSPSdtv6-OTnNq8U=g@mail.gmail.com>


> 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.

HTH

> 
> *Thanks, Keren *
> 
> On Wed, Nov 9, 2016 at 4:50 PM, Olivier Matz <olivier.matz@6wind.com> wrote:
> 
>> Hi Keren,
>> 
>> On 11/09/2016 03:40 PM, Keren Hochman wrote:
>>> On Wed, Nov 9, 2016 at 3:40 PM, Christian Ehrhardt <
>>> christian.ehrhardt@canonical.com> wrote:
>>> 
>>>> 
>>>> On Wed, Nov 9, 2016 at 1:55 PM, Keren Hochman <
>>>> keren.hochman@lightcyber.com> wrote:
>>>> 
>>>>> how can I create mempool without hugepages?My application is running
>> on a
>>>>> pcap file so no huge pages is needed ?
>>>>> 
>>>> 
>>>> Not sure if that is what you really want (Debug use only), but in
>> general
>>>> no-huge is available as EAL arg
>>>> 
>>>> From http://pktgen.readthedocs.io/en/latest/usage_eal.html :
>>>> 
>>>> EAL options for DEBUG use only:
>>>>  --no-huge           : Use malloc instead of hugetlbfs
>>>> 
>>> I need this option only for testing. How can I use rte_mempool_create if
>> I
>>> use --no-huge?
>> 
>> When using --no-huge, the dpdk libraries (including mempool) allocate
>> its memory in standard memory. Just keep in mind the physical addresses
>> will be wrong, so this memory cannot be given to hw devices.
>> 
>> Regards,
>> Olivier
>> 

Regards,
Keith

  reply	other threads:[~2016-11-10 13:11 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 [this message]
2016-11-10 13:34           ` Olivier Matz

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=6BBBABF1-45E1-4260-BE26-9C556C47B825@intel.com \
    --to=keith.wiles@intel.com \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=keren.hochman@lightcyber.com \
    --cc=olivier.matz@6wind.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).