[dpdk-dev] [PATCH] Add rte_mempool_free

2016-05-17 Thread Olivier MATZ
Hello Benjamin, On 05/16/2016 09:56 PM, Walker, Benjamin wrote: > On Mon, 2016-05-16 at 16:57 +, Wiles, Keith wrote: >>> >>> There is no inverse of rte_mempool_create, so this patch adds one. >>> The typical usage of rte_mempool_create is to create a pool at >>> initialization time and only to

[dpdk-dev] [PATCH] Add rte_mempool_free

2016-05-17 Thread Simon Kågström
Thanks for adding this, I've been missing this function! On 2016-05-16 21:56, Walker, Benjamin wrote: > On Mon, 2016-05-16 at 16:57 +, Wiles, Keith wrote: >> The big question is how do you know the mempool is not being used someplace? > > That's the user's responsibility. Use after free is c

[dpdk-dev] [PATCH] Add rte_mempool_free

2016-05-16 Thread Walker, Benjamin
On Mon, 2016-05-16 at 16:57 +, Wiles, Keith wrote: > > > > There is no inverse of rte_mempool_create, so this patch adds one. > > The typical usage of rte_mempool_create is to create a pool at > > initialization time and only to free it upon program exit, so an > > rte_mempool_free function at

[dpdk-dev] [PATCH] Add rte_mempool_free

2016-05-16 Thread Wiles, Keith
>There is no inverse of rte_mempool_create, so this patch adds one. >The typical usage of rte_mempool_create is to create a pool at >initialization time and only to free it upon program exit, so an >rte_mempool_free function at first seems to be of little value. >However, it is very useful as a san

[dpdk-dev] [PATCH] Add rte_mempool_free

2016-05-16 Thread Ben Walker
There is no inverse of rte_mempool_create, so this patch adds one. The typical usage of rte_mempool_create is to create a pool at initialization time and only to free it upon program exit, so an rte_mempool_free function at first seems to be of little value. However, it is very useful as a sanity c