From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier MATZ Subject: Re: RTE Ring removing Date: Wed, 07 May 2014 17:37:47 +0200 Message-ID: <536A534B.6030306@6wind.com> References: <5368A5E0.8090903@arccn.ru> <5369E6AF.4040402@arccn.ru> <536A1B5C.2010201@6wind.com> <1FD9B82B8BF2CF418D9A1000154491D9740A339F@ORSMSX102.amr.corp.intel.com> <536A4CB3.9000005@6wind.com> <2601191342CEEE43887BDE71AB9772580EFA401D@IRSMSX105.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: "Ananyev, Konstantin" , "Venkatesan, Venky" , Igor Ryzhov , "dev-VfR2kkLFssw@public.gmane.org" Return-path: In-Reply-To: <2601191342CEEE43887BDE71AB9772580EFA401D-kPTMFJFq+rEu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" Hi Konstantin, On 05/07/2014 05:19 PM, Ananyev, Konstantin wrote: > Just to clarify about mempool - I suppose you are talking about > ability to place internal ring and mempool metadata inside externally > allocated memory? Yes, exactly. > It is already possible to keep mempool elements inside externally > allocated memory (rte_mempool_xmem_create()). You are right, but I think the current API is a bit too complex. For instance the function rte_mempool_xmem_create() has 15 arguments which is probably too much. Anyway, as soon as I'll have a patch to show, I'll send it to the mailing list so we can discuss it. Regards, Olivier