From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 0C110374 for ; Mon, 26 Jun 2017 17:33:51 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga105.fm.intel.com with ESMTP; 26 Jun 2017 08:33:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,396,1493708400"; d="scan'208";a="985340737" Received: from smonroyx-mobl.ger.corp.intel.com (HELO [10.237.221.32]) ([10.237.221.32]) by orsmga003.jf.intel.com with ESMTP; 26 Jun 2017 08:33:48 -0700 To: Ilya Maximets , dev@dpdk.org, Thomas Monjalon , Bruce Richardson References: <1498032250-24924-1-git-send-email-i.maximets@samsung.com> <1498039711-26570-1-git-send-email-i.maximets@samsung.com> <474367ef-6d51-652a-936e-1eb90fda0bd9@samsung.com> Cc: David Marchand , Heetae Ahn , Yuanhan Liu , Jianfeng Tan , Neil Horman , Yulong Pei , Jerin Jacob From: Sergio Gonzalez Monroy Message-ID: <1bd98f0a-2668-baee-1ee3-e1fc715b6841@intel.com> Date: Mon, 26 Jun 2017 16:33:47 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <474367ef-6d51-652a-936e-1eb90fda0bd9@samsung.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v7 0/2] Balanced allocation of hugepages X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 15:33:52 -0000 On 26/06/2017 11:44, Ilya Maximets wrote: > So, what do you think about this version? > Is it ready for merge or some additional changes needed? I was just having another look at it and was wondering if we should re-set the old policy instead of DEFAULT? Also noticed that we probably should increase essential_memory by hugepage_sz in case of SIGBUS? I think there is an issue if we have more than one size. Thanks, Sergio > Best regards, Ilya Maximets. > > On 21.06.2017 13:08, Ilya Maximets wrote: >> Version 7: >> * RTE_LIBRTE_EAL_NUMA_AWARE_HUGEPAGES --> RTE_EAL_NUMA_AWARE_HUGEPAGES >> >> Version 6: >> * Configuration option RTE_LIBRTE_EAL_NUMA_AWARE_HUGEPAGES >> returned. Enabled by default for x86, ppc and thunderx. >> >> Version 5: >> * Fixed shared build. (Automated build test will fail >> anyway because libnuma-devel not installed on build servers) >> >> Version 4: >> * Fixed work on systems without NUMA by adding check for NUMA >> support in kernel. >> >> Version 3: >> * Implemented hybrid schema for allocation. >> * Fixed not needed mempolicy change while remapping. (orig = 0) >> * Added patch to enable VHOST_NUMA by default. >> >> Version 2: >> * rebased (fuzz in Makefile) >> >> Ilya Maximets (2): >> mem: balanced allocation of hugepages >> config: enable vhost numa awareness by default >> >> config/common_base | 1 + >> config/common_linuxapp | 3 + >> config/defconfig_arm-armv7a-linuxapp-gcc | 4 + >> config/defconfig_arm64-armv8a-linuxapp-gcc | 4 + >> config/defconfig_arm64-thunderx-linuxapp-gcc | 4 + >> lib/librte_eal/linuxapp/eal/Makefile | 3 + >> lib/librte_eal/linuxapp/eal/eal_memory.c | 105 ++++++++++++++++++++++++++- >> mk/rte.app.mk | 3 + >> 8 files changed, 123 insertions(+), 4 deletions(-) >>