From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id F18FFADA7 for ; Thu, 16 Apr 2015 11:26:06 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 16 Apr 2015 02:26:06 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,586,1422950400"; d="scan'208";a="710075529" Received: from smonroyx-mobl.ger.corp.intel.com (HELO [10.237.220.60]) ([10.237.220.60]) by fmsmga002.fm.intel.com with ESMTP; 16 Apr 2015 02:26:05 -0700 Message-ID: <552F802C.1040208@intel.com> Date: Thu, 16 Apr 2015 10:26:04 +0100 From: "Gonzalez Monroy, Sergio" User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Marc Sune References: <552EB8C6.5050906@linaro.org> <20150415122419.767e4048@urahara> <552F7AD6.3070003@intel.com> <552F7F46.7050000@bisdn.de> In-Reply-To: <552F7F46.7050000@bisdn.de> 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: Thu, 16 Apr 2015 09:26:07 -0000 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' :) Sergio