From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Gonzalez Monroy, Sergio" Subject: Re: [PATCH v8 0/9] Dynamic memzones Date: Wed, 14 Oct 2015 12:05:18 +0100 Message-ID: <561E36EE.3020504@intel.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Stephen Hemminger 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) In-Reply-To: <20151013171200.0a994215@xeon-e3> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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