From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 9404C8D9A for ; Wed, 14 Oct 2015 13:05:21 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga102.jf.intel.com with ESMTP; 14 Oct 2015 04:05:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,681,1437462000"; d="scan'208";a="826648086" Received: from smonroyx-mobl.ger.corp.intel.com (HELO [10.237.220.114]) ([10.237.220.114]) by fmsmga002.fm.intel.com with ESMTP; 14 Oct 2015 04:05:19 -0700 From: "Gonzalez Monroy, Sergio" To: Stephen Hemminger References: <1435917343-23032-1-git-send-email-sergio.gonzalez.monroy@intel.com> <1436864233-24746-1-git-send-email-sergio.gonzalez.monroy@intel.com> <20151013171200.0a994215@xeon-e3> Message-ID: <561E36EE.3020504@intel.com> Date: Wed, 14 Oct 2015 12:05:18 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151013171200.0a994215@xeon-e3> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v8 0/9] Dynamic memzones 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: Wed, 14 Oct 2015 11:05:22 -0000 On 14/10/2015 01:12, Stephen Hemminger wrote: > On Tue, 14 Jul 2015 09:57:04 +0100 > Sergio Gonzalez Monroy wrote: > >> Current implemetation allows reserving/creating memzones but not the opposite >> (unreserve/free). This affects mempools and other memzone based objects. >> >> From my point of view, implementing free functionality for memzones would look >> like malloc over memsegs. >> Thus, this approach moves malloc inside eal (which in turn removes a circular >> dependency), where malloc heaps are composed of memsegs. >> We keep both malloc and memzone APIs as they are, but memzones allocate its >> memory by calling malloc_heap_alloc. >> Some extra functionality is required in malloc to allow for boundary constrained >> memory requests. >> In summary, currently malloc is based on memzones, and with this approach >> memzones are based on malloc. >> >> v8: >> - Rebase against current HEAD to factor for changes made by new Tile-Gx arch > Following rules in kernel. You need to fix the 32 bit build and resubmit whole > series. > > Thomas, this patchset should be marked "Changes requested" in patchwork. The v10 patchset was applied in 2.1. Could you elaborate on the issue? I can build without errors for target i686-native-linuxapp-gcc Sergio