From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com
 [209.85.220.53]) by dpdk.org (Postfix) with ESMTP id 9AC208D9D
 for <dev@dpdk.org>; Wed, 14 Oct 2015 02:11:50 +0200 (CEST)
Received: by pabws5 with SMTP id ws5so4680145pab.1
 for <dev@dpdk.org>; Tue, 13 Oct 2015 17:11:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=HEESC1WPnHkjkBNwXvqKVywXtp5DlMRJmVj/ooxz5so=;
 b=ZHTa5OMZYxF+9ven5cUQPzCldpX5usXNGTidiAO9BZnDqo3iG2g04tsT7FMvxUoNbI
 g8qorQCuv6dTwVV+ZrBErhevvC/3axZwAdqkjRvz0ozMcEdIk4SlCZFJsXJyp+46hxrk
 nkd8LpZt7eWCsoOuQ8oMcf52bdMKkdN8hHpYoWRM5HJKITzpABKh4AdnUegq5oackEP7
 x42YtRterYEdHxPDQl5bAEJicxseq8q9kHKFXj6Cds6Is6DZEtxAbAtypgk8RDaVz/aJ
 t7hMdedVVxyzBNXI6f1tHY72mpp9jKse/Dc5uOnemUu+6VjyAaTmjo0p4sYkkk4726TL
 /Kjg==
X-Gm-Message-State: ALoCoQnpRJde9T7EUE/63ShmI0pPT9es1UyYouPDRQVkA7UWlYiRs2ohhmz8YUKQP0acnqc2wCn7
X-Received: by 10.68.131.68 with SMTP id ok4mr218744pbb.149.1444781509008;
 Tue, 13 Oct 2015 17:11:49 -0700 (PDT)
Received: from xeon-e3 (static-50-53-82-155.bvtn.or.frontiernet.net.
 [50.53.82.155])
 by smtp.gmail.com with ESMTPSA id y5sm5935790pbt.77.2015.10.13.17.11.48
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 13 Oct 2015 17:11:48 -0700 (PDT)
Date: Tue, 13 Oct 2015 17:12:00 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>, Thomas
 Monjalon <thomas.monjalon@6wind.com>
Message-ID: <20151013171200.0a994215@xeon-e3>
In-Reply-To: <1436864233-24746-1-git-send-email-sergio.gonzalez.monroy@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2015 00:11:51 -0000

On Tue, 14 Jul 2015 09:57:04 +0100
Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> 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.