Re: [ovs-dev] [ovs-dev,V2] netdev-dpdk: fix memory leak

2016-08-08 Thread Kavanagh, Mark B
> >Thanks for the report, I didn't realize that the callback could come in the >same thread. > Likewise - thanks for the catch, Ilya. >I sent a patch that I believe should fix the deadlock here: Thanks for resolving the issue, Daniele. > >http://openvswitch.org/pipermail/dev/2016-August/077315

Re: [ovs-dev] [ovs-dev,V2] netdev-dpdk: fix memory leak

2016-08-05 Thread Daniele Di Proietto
Thanks for the report, I didn't realize that the callback could come in the same thread. I sent a patch that I believe should fix the deadlock here: http://openvswitch.org/pipermail/dev/2016-August/077315.html 2016-08-05 7:48 GMT-07:00 Ilya Maximets : > On 04.08.2016 12:49, Mark Kavanagh wrote:

Re: [ovs-dev] [ovs-dev,V2] netdev-dpdk: fix memory leak

2016-08-05 Thread Ilya Maximets
On 04.08.2016 12:49, Mark Kavanagh wrote: > DPDK v16.07 introduces the ability to free memzones. > Up until this point, DPDK memory pools created in OVS could > not be destroyed, thus incurring a memory leak. > > Leverage the DPDK v16.07 rte_mempool API to free DPDK > mempools when their associate