Re: [dpdk-dev] disable hugepages

[Keren Hochman <keren.hochman@lightcyber.com>]

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?

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