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 9988A592B for ; Fri, 22 May 2015 10:30:58 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga102.fm.intel.com with ESMTP; 22 May 2015 01:30:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,474,1427785200"; d="scan'208";a="698780597" Received: from smonroyx-mobl.ger.corp.intel.com (HELO [10.237.220.49]) ([10.237.220.49]) by orsmga001.jf.intel.com with ESMTP; 22 May 2015 01:30:56 -0700 Message-ID: <555EE93F.3080508@intel.com> Date: Fri, 22 May 2015 09:30:55 +0100 From: "Gonzalez Monroy, Sergio" User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Harish Patil References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] freeing memzone 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, 22 May 2015 08:30:59 -0000 On 21/05/2015 17:59, Harish Patil wrote: > Hello dpdk-dev, > > I understand that the reserved memzones cannot be freed, as mentioned in > the DPDK specs. But I would like to know why? Is there any limitations? There should be a few threads in the mailing list related to this topic. Last that comes to mind: http://dpdk.org/ml/archives/dev/2015-April/016501.html Short answer is, it has not been implemented yet. > If the memory is not freed/returned, then can it be reused for subsequent > allocations without re-init (i.e. with same memzone name)? > We use it for allocating DMA’ble memory. It is up to the application to manage the use/re-use of memzones. By the way, would maybe rte_malloc memory be more suitable than memzones for your application? You can retrieve the physical address of memory allcoated by rte_malloc with rte_malloc_virt2phy. > Secondly, there was a related discussion on this in the following email > thread: > http://dpdk.org/ml/archives/dev/2014-July/004456.html > > Do we plan to incorporate that changes? There is some ongoing work related to freeing memzones: http://dpdk.org/ml/archives/dev/2015-May/017470.html Feel free to comment on it. Sergio > Thanks, > Harish > > > ________________________________ > > This message and any attached documents contain information from the sending company or its parent company(s), subsidiaries, divisions or branch offices that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.