From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <olivier.matz@6wind.com>
Received: from proxy.6wind.com (host.76.145.23.62.rev.coltfrance.com
 [62.23.145.76]) by dpdk.org (Postfix) with ESMTP id ECEAB5A95
 for <dev@dpdk.org>; Tue, 17 May 2016 09:33:04 +0200 (CEST)
Received: from [10.16.0.195] (unknown [10.16.0.195])
 by proxy.6wind.com (Postfix) with ESMTP id E756923D7E;
 Tue, 17 May 2016 09:31:27 +0200 (CEST)
To: "Walker, Benjamin" <benjamin.walker@intel.com>,
 "Wiles, Keith" <keith.wiles@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
References: <1463416935-82998-1-git-send-email-benjamin.walker@intel.com>
 <815F2AB2-EBA1-4097-91B6-14DDD18497BE@intel.com>
 <1463428590.2522.160.camel@intel.com>
From: Olivier MATZ <olivier.matz@6wind.com>
Message-ID: <573AC923.8070706@6wind.com>
Date: Tue, 17 May 2016 09:32:51 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Icedove/38.6.0
MIME-Version: 1.0
In-Reply-To: <1463428590.2522.160.camel@intel.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-dev] [PATCH] Add rte_mempool_free
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: Tue, 17 May 2016 07:33:05 -0000

Hello Benjamin,

On 05/16/2016 09:56 PM, Walker, Benjamin wrote:
> On Mon, 2016-05-16 at 16:57 +0000, Wiles, Keith wrote:
>>>
>>> There is no inverse of rte_mempool_create, so this patch adds one.
>>> The typical usage of rte_mempool_create is to create a pool at
>>> initialization time and only to free it upon program exit, so an
>>> rte_mempool_free function at first seems to be of little value.
>>> However, it is very useful as a sanity check for a clean shutdown
>>> when used in conjunction with tools like AddressSanitizer. Further,
>>> the call itself verifies that all elements have been returned to
>>> the pool or it fails.
>>>
>>> Signed-off-by: Ben Walker <benjamin.walker@intel.com>

I already submitted a patch introducing a similar feature.
Please see:
http://dpdk.org/dev/patchwork/patch/12062/

It is part of a larger patchset:
http://dpdk.org/ml/archives/dev/2016-April/037464.html


Regards,
Olivier