[dpdk-dev] [PATCH v2] app/test: fix memory needs after RTE_MAX_LCORE was increased to 128
Thomas Monjalon
thomas.monjalon at 6wind.com
Thu Dec 11 02:11:04 CET 2014
2014-12-10 15:40, Thomas Monjalon:
> 2014-12-09 10:11, Pablo de Lara:
> > Since commit b91c67e5a693211862aa7dc3b78630b4e856c2af,
> > maximum number of cores is 128, which has increase
> > the total memory necessary for a rte_mempool structure,
> > as the per-lcore local cache has been doubled in size.
> > Therefore, eal_flags unit test was broken since it needed
> > to use more hugepages.
> >
> > Changes in v2: Increased memory to 18MB, as that is the
> > actual minimum memory necessary (depending on the physical memory segments,
> > DPDK may need less memory)
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch at intel.com>
>
> Independently of RTE_MAX_LCORE being increased to 128, I still have some
> problems with test_invalid_vdev_flag().
> First, DEFAULT_MEM_SIZE is not used in this function.
> Also, even with your patch, I get this error in my VM:
> Cannot get hugepage information
>
> But if this patch solves an issue for you, I guess it should be applied.
> That said, I would appreciate a complete description of the commands
> you use to launch this test in a VM (starting with the Qemu command).
Applied
I think we should try to improve this test to be able to run it everywhere.
Thanks
--
Thomas
More information about the dev
mailing list