From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx.bisdn.de (mx.bisdn.de [185.27.182.31]) by dpdk.org (Postfix) with ESMTP id BD77B6942 for ; Fri, 17 Apr 2015 10:32:52 +0200 (CEST) Received: from [172.16.250.156] (unknown [172.16.250.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.bisdn.de (Postfix) with ESMTPSA id 678CDA3B36; Fri, 17 Apr 2015 10:32:52 +0200 (CEST) Message-ID: <5530C530.5060500@bisdn.de> Date: Fri, 17 Apr 2015 10:32:48 +0200 From: Marc Sune User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: "Gonzalez Monroy, Sergio" References: <552EB8C6.5050906@linaro.org> <20150415122419.767e4048@urahara> <552F7AD6.3070003@intel.com> <552F7F46.7050000@bisdn.de> <552F802C.1040208@intel.com> In-Reply-To: <552F802C.1040208@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org Subject: Re: [dpdk-dev] mempool deleting and cache_size 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: Fri, 17 Apr 2015 08:32:53 -0000 On 16/04/15 11:26, Gonzalez Monroy, Sergio wrote: > On 16/04/2015 10:22, Marc Sune wrote: >> >> >> On 16/04/15 11:03, Gonzalez Monroy, Sergio wrote: >>> On 15/04/2015 20:24, Stephen Hemminger wrote: >>>> On Wed, 15 Apr 2015 20:15:18 +0100 >>>> Zoltan Kiss wrote: >>>> >>>>> Hi, >>>>> >>>>> I have two questions regarding mempools: >>>>> >>>>> - the first is trivial: how do you delete them? Can you? I can't >>>>> see a >>>>> function to do that, and none of the examples are doing such >>>>> thing. When >>>>> exactly it get deleted? >>>> You can't delete them. They live in hugepage area and are persistent. >>>> Correctly written code looks for them by name and reuses existing pool >>>> if it is big enough. >>>> >>> FYI, I'm looking into such functionality and also delete/destroy >>> mempools (although still no plan on implementation). >>> >> >> Also the memzones behind, or will be "lost/leaked" after a mempool >> destruction? >> >> Marc >> >>> Sergio >> > Sorry, my bad. > I did mean to say 'delete/destroy memzones' :) Good, That would make the KNI memzone pool not necessary anymore: http://article.gmane.org/gmane.comp.networking.dpdk.devel/6890/ If your patch gets accepted I will adapt that. Marc > > Sergio