Re: [dpdk-dev] [PATCH 2/2] timer: fix resource leak in finalize

2019-07-04 Thread David Marchand
On Thu, Jul 4, 2019 at 12:45 PM Burakov, Anatoly wrote: > On 04-Jul-19 10:10 AM, David Marchand wrote: > > On Tue, Jun 25, 2019 at 6:12 PM Anatoly Burakov < > anatoly.bura...@intel.com> > > wrote: > > > >> Currently, whenever timer library is initialized, the memory is leaked > >> because there i

Re: [dpdk-dev] [PATCH 2/2] timer: fix resource leak in finalize

2019-07-04 Thread Burakov, Anatoly
On 04-Jul-19 10:10 AM, David Marchand wrote: On Tue, Jun 25, 2019 at 6:12 PM Anatoly Burakov wrote: Currently, whenever timer library is initialized, the memory is leaked because there is no telling when primary or secondary processes get to use the state, and there is no way to initialize/dei

Re: [dpdk-dev] [PATCH 2/2] timer: fix resource leak in finalize

2019-07-04 Thread David Marchand
On Tue, Jun 25, 2019 at 6:12 PM Anatoly Burakov wrote: > Currently, whenever timer library is initialized, the memory is leaked > because there is no telling when primary or secondary processes get > to use the state, and there is no way to initialize/deinitialize > timer library state without ra

Re: [dpdk-dev] [PATCH 2/2] timer: fix resource leak in finalize

2019-06-27 Thread Carrillo, Erik G
> -Original Message- > From: Burakov, Anatoly > Sent: Tuesday, June 25, 2019 11:12 AM > To: dev@dpdk.org > Cc: Robert Sanford ; Carrillo, Erik G > > Subject: [PATCH 2/2] timer: fix resource leak in finalize > > Currently, whenever timer library is initialized, the memory is leaked because

[dpdk-dev] [PATCH 2/2] timer: fix resource leak in finalize

2019-06-25 Thread Anatoly Burakov
Currently, whenever timer library is initialized, the memory is leaked because there is no telling when primary or secondary processes get to use the state, and there is no way to initialize/deinitialize timer library state without race conditions because the data itself must live in shared memory.