[dpdk-dev] [PATCH v4 14/17] mempool: add support to non-EAL thread

2015-02-10 Thread Liang, Cunming
> -Original Message- > From: Olivier MATZ [mailto:olivier.matz at 6wind.com] > Sent: Tuesday, February 10, 2015 1:52 AM > To: Liang, Cunming; dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH v4 14/17] mempool: add support to non-EAL > thread > > Hi, > >

[dpdk-dev] [PATCH v4 14/17] mempool: add support to non-EAL thread

2015-02-09 Thread Olivier MATZ
Hi, On 02/09/2015 03:41 PM, Liang, Cunming wrote: >>> #ifdef RTE_LIBRTE_MEMPOOL_DEBUG >>> -#define __MEMPOOL_STAT_ADD(mp, name, n) do { \ >>> - unsigned __lcore_id = rte_lcore_id(); \ >>> - mp->stats[__lcore_id].name##_objs += n; \ >>>

[dpdk-dev] [PATCH v4 14/17] mempool: add support to non-EAL thread

2015-02-09 Thread Liang, Cunming
> -Original Message- > From: Olivier MATZ [mailto:olivier.matz at 6wind.com] > Sent: Monday, February 09, 2015 4:01 AM > To: Liang, Cunming; dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH v4 14/17] mempool: add support to non-EAL > thread > > Hi, > > O

[dpdk-dev] [PATCH v4 14/17] mempool: add support to non-EAL thread

2015-02-08 Thread Olivier MATZ
Hi, On 02/02/2015 03:02 AM, Cunming Liang wrote: > For non-EAL thread, bypass per lcore cache, directly use ring pool. > It allows using rte_mempool in either EAL thread or any user pthread. > As in non-EAL thread, it directly rely on rte_ring and it's none preemptive. > It doesn't suggest to run

[dpdk-dev] [PATCH v4 14/17] mempool: add support to non-EAL thread

2015-02-02 Thread Cunming Liang
For non-EAL thread, bypass per lcore cache, directly use ring pool. It allows using rte_mempool in either EAL thread or any user pthread. As in non-EAL thread, it directly rely on rte_ring and it's none preemptive. It doesn't suggest to run multi-pthread/cpu which compete the rte_mempool. It will