[dpdk-dev] [PATCH 10/36] mempool: use the list to iterate the mempool elements

>Hi, > >On 04/14/2016 05:33 PM, Wiles, Keith wrote: >>> >>> static void >>> -txq_mp2mr_mbuf_check(void *arg, void *start, void *end, >>> -uint32_t index __rte_unused) >>> +txq_mp2mr_mbuf_check(struct rte_mempool *mp, void *arg, void *obj, >>> + __rte_unused uint32_t index) >> >>

[dpdk-dev] [PATCH 10/36] mempool: use the list to iterate the mempool elements

Hi, On 04/14/2016 05:33 PM, Wiles, Keith wrote: >> >> static void >> -txq_mp2mr_mbuf_check(void *arg, void *start, void *end, >> - uint32_t index __rte_unused) >> +txq_mp2mr_mbuf_check(struct rte_mempool *mp, void *arg, void *obj, >> +__rte_unused uint32_t index) > > I have se

[dpdk-dev] [PATCH 10/36] mempool: use the list to iterate the mempool elements

> > static void >-txq_mp2mr_mbuf_check(void *arg, void *start, void *end, >- uint32_t index __rte_unused) >+txq_mp2mr_mbuf_check(struct rte_mempool *mp, void *arg, void *obj, >+ __rte_unused uint32_t index) I have seen this use of __rte_unused or attributes attached to varia

[dpdk-dev] [PATCH 10/36] mempool: use the list to iterate the mempool elements

Now that the mempool objects are chained into a list, we can use it to browse them. This implies a rework of rte_mempool_obj_iter() API, that does not need to take as many arguments as before. The previous function is kept as a private function, and renamed in this commit. It will be removed in a n