From: Olivier Matz <olivier.matz@6wind.com>
To: Keren Hochman <keren.hochman@lightcyber.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] disable hugepages
Date: Wed, 9 Nov 2016 15:50:02 +0100 [thread overview]
Message-ID: <af2edd56-f900-4317-2d78-f7c6051e8502@6wind.com> (raw)
In-Reply-To: <CAJq3SQ7r4e_Dr1wvwPYmiECWASEvAwvZomH4x6o1MFo35JQVXg@mail.gmail.com>
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
next prev parent reply other threads:[~2016-11-09 14:50 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 [this message]
2016-11-10 12:32 ` Keren Hochman
2016-11-10 13:10 ` Wiles, Keith
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=af2edd56-f900-4317-2d78-f7c6051e8502@6wind.com \
--to=olivier.matz@6wind.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--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).