From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) by dpdk.org (Postfix) with ESMTP id AFF777E79 for ; Thu, 11 Dec 2014 02:11:42 +0100 (CET) Received: by mail-wi0-f181.google.com with SMTP id r20so7059776wiv.2 for ; Wed, 10 Dec 2014 17:11:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=tCT6g+n2mIG5JXqhOTPb27OusotVyeAVAwlhQl8bVso=; b=L5K9QXDG8voKYKMm8Mu6NNlpgueMxe84deofVsEyGC5KFI4uP8TyM8UU0EMTkeEA6E wpF3V8YgLDHi+G8Y68oHwW/9NUEQ8J3i6zBwkx2xzb+9Q8U5XBosQnRsr5Xf6VkLf5/4 u0k172kJTnGmJgmjiZnZX0SDDQ6c1BI/yIqxNwFHzll2wrS6Oba1ERJAREjwnlxDFhU9 qvyplWAh0mvddksIUCxv1kbAIATHItJYwhCddTigwm+DP9clshlTuMX62jqd84AycTA1 rtd2voa8xzOmUlQOUKIMeAbxNf8N3iGNsrYFOJB3A4BQucXkJAu5EUYqVQI0fLwmJDwl HOQw== X-Gm-Message-State: ALoCoQkZYiEK5bSgW6gHqR46LpH4EzTV82ciGo2Omff5hXT5TP3xFBLnVWDWsPpcfEDycIpTZiyw X-Received: by 10.180.211.201 with SMTP id ne9mr17512399wic.30.1418260302505; Wed, 10 Dec 2014 17:11:42 -0800 (PST) Received: from xps13.localnet ([88.249.222.12]) by mx.google.com with ESMTPSA id n3sm824768wiw.5.2014.12.10.17.11.41 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Dec 2014 17:11:41 -0800 (PST) From: Thomas Monjalon To: Pablo de Lara Date: Thu, 11 Dec 2014 02:11:04 +0100 Message-ID: <6865201.6y9pmue6ZI@xps13> Organization: 6WIND User-Agent: KMail/4.14.3 (Linux/3.17.4-1-ARCH; KDE/4.14.3; x86_64; ; ) In-Reply-To: <1437499.n9ubl6fXCh@xps13> References: <1417696834-21354-1-git-send-email-pablo.de.lara.guarch@intel.com> <1418119872-15335-1-git-send-email-pablo.de.lara.guarch@intel.com> <1437499.n9ubl6fXCh@xps13> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v2] app/test: fix memory needs after RTE_MAX_LCORE was increased to 128 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2014 01:11:43 -0000 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 > > 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