From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51])
 by dpdk.org (Postfix) with ESMTP id 161AAC320
 for <dev@dpdk.org>; Thu, 16 Jul 2015 14:06:43 +0200 (CEST)
Received: by wgxm20 with SMTP id m20so56682531wgx.3
 for <dev@dpdk.org>; Thu, 16 Jul 2015 05:06:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=bkXpOS9zsNF2rWSJ7l5XGK82DXNw2WMwSzslAfz986I=;
 b=CeyFLSVMe5BbkUrTZP9rdX1NKKMwfEqiee1jF8P9tPrLw7imARhEGTKJiv0uVJB9im
 8wDLLEQ15DNxxDIMPSwNBLyou7p8OB5boGyX4Tl0iW3LNXL7hTp9jF1Pa3VY5XhmeqcT
 6ABAvIOBnoIi+37a2cmHLzc0ew0W2P/3j/BOPYFDg1IS2RGPn8CFFkaxLiRorTF54i9X
 F+YGscyKtuK72M5lUptRZQsc865iDR5NRDxHESx9qjljL8cHc29jtCKED4NlwIpyJwaW
 eUEQA2lCcBstboZ6JIZsW5N50nVtti1siQitedT+iAX1yGT7xaZXnxkPglRvzRRH6MRS
 9zoQ==
X-Gm-Message-State: ALoCoQntpJd+3Q0dPbSSKcow64ImT8zAMD6ppB86qfz171eWZYuBgBMSewyarGgkfuC5+pe1hiR9
X-Received: by 10.194.48.8 with SMTP id h8mr18933205wjn.82.1437048402919;
 Thu, 16 Jul 2015 05:06:42 -0700 (PDT)
Received: from xps13.localnet (6wind.net2.nerim.net. [213.41.151.210])
 by smtp.gmail.com with ESMTPSA id bm9sm2839452wib.10.2015.07.16.05.06.41
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Thu, 16 Jul 2015 05:06:41 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Date: Thu, 16 Jul 2015 14:05:31 +0200
Message-ID: <8355871.YHnrBBomrZ@xps13>
Organization: 6WIND
User-Agent: KMail/4.14.8 (Linux/4.0.4-2-ARCH; KDE/4.14.8; x86_64; ; )
In-Reply-To: <1436977948-589-1-git-send-email-sergio.gonzalez.monroy@intel.com>
References: <1436948793-12867-1-git-send-email-sergio.gonzalez.monroy@intel.com>
 <1436977948-589-1-git-send-email-sergio.gonzalez.monroy@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v10 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: Thu, 16 Jul 2015 12:06:43 -0000

2015-07-15 17:32, Sergio Gonzalez Monroy:
> 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.

Applied, thanks for the big rework.