From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerin Jacob Subject: Re: [PATCH v3 1/2] mempool: add stack (lifo) mempool handler Date: Tue, 21 Jun 2016 09:12:57 +0530 Message-ID: <20160621034256.GB4903@localhost.localdomain> References: <1463669335-30378-1-git-send-email-david.hunt@intel.com> <1466428091-115821-2-git-send-email-david.hunt@intel.com> <20160620132506.GA3301@localhost.localdomain> <3416153.NDoMD8TpjF@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: , David Hunt , , , To: Thomas Monjalon Return-path: Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0078.outbound.protection.outlook.com [157.56.111.78]) by dpdk.org (Postfix) with ESMTP id AA8ED8D93 for ; Tue, 21 Jun 2016 05:43:13 +0200 (CEST) Content-Disposition: inline In-Reply-To: <3416153.NDoMD8TpjF@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, Jun 20, 2016 at 03:54:20PM +0200, Thomas Monjalon wrote: > 2016-06-20 18:55, Jerin Jacob: > > On Mon, Jun 20, 2016 at 02:08:10PM +0100, David Hunt wrote: > > > This is a mempool handler that is useful for pipelining apps, where > > > the mempool cache doesn't really work - example, where we have one > > > core doing rx (and alloc), and another core doing Tx (and return). In > > > such a case, the mempool ring simply cycles through all the mbufs, > > > resulting in a LLC miss on every mbuf allocated when the number of > > > mbufs is large. A stack recycles buffers more effectively in this > > > case. > > > > > > Signed-off-by: David Hunt > > > --- > > > lib/librte_mempool/Makefile | 1 + > > > lib/librte_mempool/rte_mempool_stack.c | 145 +++++++++++++++++++++++++++++++++ > > > > How about moving new mempool handlers to drivers/mempool? (or similar). > > In future, adding HW specific handlers in lib/librte_mempool/ may be bad idea. > > You're probably right. > However we need to check and understand what a HW mempool handler will be. > I imagine the first of them will have to move handlers in drivers/ > Jerin, are you volunteer? Thomas, We are planning to upstream a HW based mempool handler. Not sure about the timelines. We will take up this as part of a HW based mempool upstreaming if no one takes it before that. Jerin