DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/test: fix memory needs after RTE_MAX_LCORE was increased to 128
Date: Fri, 5 Dec 2014 15:57:28 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897268746AB@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <6503818.31ZSLaLBbV@xps13>

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, December 04, 2014 1:21 PM
> To: De Lara Guarch, Pablo
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] app/test: fix memory needs after
> RTE_MAX_LCORE was increased to 128
> > 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.
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> When I check it in a VM, I still have a memory issue in
> test_invalid_vdev_flag().
> Do you have an idea of the problem?

Sorry I did not have a VM by that time. Now I do :)
Apparently it needs more memory, as first thing DPDK does is 
reserving space in rte_malloc heap, which size is bigger in the VM.
By changing the memory needed to 18M, we can fix the unit test.
I am still not sure why within a VM we need more memory, though.

> --
> Thomas

  reply	other threads:[~2014-12-05 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 12:40 Pablo de Lara
2014-12-04 13:20 ` Thomas Monjalon
2014-12-05 15:57   ` De Lara Guarch, Pablo [this message]
2014-12-09 10:11 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2014-12-10 14:40   ` Thomas Monjalon
2014-12-11  1:11     ` Thomas Monjalon
2014-12-11  9:56       ` De Lara Guarch, Pablo

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E115CCD9D858EF4F90C690B0DCB4D897268746AB@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \


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