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 <david.hunt at intel.com> > > > --- > > > 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