From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 316962BA2 for ; Thu, 8 Jun 2017 17:44:52 +0200 (CEST) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jun 2017 08:44:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,315,1493708400"; d="scan'208";a="271845800" Received: from smonroyx-mobl.ger.corp.intel.com (HELO [10.237.221.32]) ([10.237.221.32]) by fmsmga004.fm.intel.com with ESMTP; 08 Jun 2017 08:44:49 -0700 To: Bruce Richardson , Ilya Maximets References: <1496736832-835-1-git-send-email-i.maximets@samsung.com> <1496756020-4579-1-git-send-email-i.maximets@samsung.com> <6eb536e9-9071-f08e-e819-a41c6f78cda3@samsung.com> <20170608121403.GA59132@bricha3-MOBL3.ger.corp.intel.com> Cc: dev@dpdk.org, David Marchand , Thomas Monjalon , Heetae Ahn , Yuanhan Liu , Jianfeng Tan , Neil Horman , Yulong Pei From: Sergio Gonzalez Monroy Message-ID: <0d7f6aa1-8026-a051-9f8c-d80b8136a7a9@intel.com> Date: Thu, 8 Jun 2017 16:44:49 +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: <20170608121403.GA59132@bricha3-MOBL3.ger.corp.intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v5 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: Thu, 08 Jun 2017 15:44:53 -0000 On 08/06/2017 13:14, Bruce Richardson wrote: > On Thu, Jun 08, 2017 at 02:21:58PM +0300, Ilya Maximets wrote: >> Hi everyone, >> >> I just want to clarify current status of these patches. >> As I understand, moving to the new build system (for example, >> meson+ninja as proposed[1] by Bruce) is a very long process. >> But we have issues with imbalanced memory allocation now, and >> IMHO it's better to fix them in a near future. >> >> Latest version (v5) of balanced allocation patches adds linbuma >> as general unconditional dependency which conflicts with the >> current DPDK policies. >> >> So, there are 2 option: >> >> 1. Return back config option RTE_LIBRTE_EAL_NUMA_AWARE_HUGEPAGES >> from the first version of the patch and disable it by default. >> >> 2. Keep patch as it is now and make everyone install libnuma >> for successful build. >> >> I have no preferences about above options. I'm asking your opinions. >> >> Bruce, Sergio, Thomas, what do you think? >> >> [1] http://dpdk.org/ml/archives/dev/2017-June/067428.html >> >> Best regards, Ilya Maximets. >> > I would be ok with having libnuma as a dependency, so I think I'd prefer > option 2 to 1, assuming libnuma is available in all major Linux distros. > > /Bruce +1 on option 2 (current patch and libnuma as DPDK dependency). Sergio