From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 12970AFD8 for ; Wed, 7 May 2014 17:36:47 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP; 07 May 2014 08:36:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,1004,1389772800"; d="scan'208";a="527882562" Received: from fmsmsx105.amr.corp.intel.com ([10.19.9.36]) by fmsmga001.fm.intel.com with ESMTP; 07 May 2014 08:36:24 -0700 Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by FMSMSX105.amr.corp.intel.com (10.19.9.36) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 7 May 2014 08:36:24 -0700 Received: from fmsmsx105.amr.corp.intel.com ([169.254.5.106]) by FMSMSX113.amr.corp.intel.com ([169.254.4.59]) with mapi id 14.03.0123.003; Wed, 7 May 2014 08:36:24 -0700 From: "Rogers, Gerald" To: "Venkatesan, Venky" , Olivier MATZ , Igor Ryzhov , "dev@dpdk.org" Thread-Topic: [dpdk-dev] RTE Ring removing Thread-Index: AQHPaQpq7i5YPgFxpUaBizUX8wiYmZs1NmKAgAA+ywCAACfMAP//pSWA Date: Wed, 7 May 2014 15:36:23 +0000 Message-ID: References: <5368A5E0.8090903@arccn.ru> <5369E6AF.4040402@arccn.ru> <536A1B5C.2010201@6wind.com> <1FD9B82B8BF2CF418D9A1000154491D9740A339F@ORSMSX102.amr.corp.intel.com> In-Reply-To: <1FD9B82B8BF2CF418D9A1000154491D9740A339F@ORSMSX102.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.1.140326 x-originating-ip: [10.34.84.181] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <2D70D631AC4E784A840D15A9D4DEEF78@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] RTE Ring removing 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: Wed, 07 May 2014 15:36:48 -0000 Venky, This also applies to mbuf pools. Inside of the openvswitch.org patches we allocate mbuf pools for a port, but we are unable to free them back when the port is removed. One other request (maybe it is there, and I=B9m unaware), is the ability to dynamically add / remove a physical port to DPDK. Basically we should be able to reassign on the fly a port from the kernel to DPDK, and vice versa (of course with the caveat that all structures be released in both environments and a port reinitialized). Gerald On 5/7/14, 7:01 AM, "Venkatesan, Venky" wrote: >Olivier,=20 > >We should look at how to make the memseg capable of doing alloc/free >(including re-assembly of fragments) after the 1.7 release. Is that >something you are considering doing (or are there any other DPDKers >considering this), or should I look at putting together a patch for that? > >Regards,=20 >-Venky > >-----Original Message----- >From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier MATZ >Sent: Wednesday, May 07, 2014 4:39 AM >To: Igor Ryzhov; dev@dpdk.org >Subject: Re: [dpdk-dev] RTE Ring removing > >Hi Igor, > >On 05/07/2014 09:54 AM, Igor Ryzhov wrote: >> I noticed that in Memzone realization there is a special global >> variable "free_memseg" containing pointers on free memory segments. >> An memzone reserve function just finst the best segment for allocation >> from this "free_memseg" variable. >> >> So I think there is a possibility to unreserve already reserved memory >> back to "free_memseg", and impossibility of unreserving memory is just >> because there is no function for that, not because it is impossible in >> principle. >> Am I right? Or there are any restrictions? > >I think that implementing a freeing of memory segment is feasible, but it >would require some work to properly merge freed zones to avoid memory >fragmentation. > >Another solution is to allocate/free rings in standard memory (malloc for >instance) instead of rte_memzones. Let me know if the patches I've just >sent on the mailing list solves your issue. > >By the way, I plan to do the same thing for mempools in the coming weeks >but there is much more work. > >Regards, >Olivier >