[dpdk-dev] [PATCH v3 3/3] mempool: allow for user-owned mempool caches

2016-06-20 Thread Olivier Matz
Hi, On 06/18/2016 06:15 PM, Lazaros Koromilas wrote: >> What do you think of having: >> >> #define LOG_ERR() do { \ >> printf("test failed at %s():%d\n", __func__, __LINE__); \ >> } while (0) >> #define RET_ERR() do { LOG_ERR(); return -1; }

[dpdk-dev] [PATCH v3 3/3] mempool: allow for user-owned mempool caches

2016-06-18 Thread Lazaros Koromilas
On Fri, Jun 17, 2016 at 11:37 AM, Olivier Matz wrote: > > > On 06/16/2016 01:02 PM, Lazaros Koromilas wrote: >> The mempool cache is only available to EAL threads as a per-lcore >> resource. Change this so that the user can create and provide their own >> cache on mempool get and put operations.

[dpdk-dev] [PATCH v3 3/3] mempool: allow for user-owned mempool caches

2016-06-17 Thread Olivier Matz
On 06/16/2016 01:02 PM, Lazaros Koromilas wrote: > The mempool cache is only available to EAL threads as a per-lcore > resource. Change this so that the user can create and provide their own > cache on mempool get and put operations. This works with non-EAL threads > too. This commit introduces t

[dpdk-dev] [PATCH v3 3/3] mempool: allow for user-owned mempool caches

2016-06-16 Thread Lazaros Koromilas
The mempool cache is only available to EAL threads as a per-lcore resource. Change this so that the user can create and provide their own cache on mempool get and put operations. This works with non-EAL threads too. This commit introduces the new API calls: rte_mempool_cache_create(size, socke