Re: [dpdk-dev] [PATCH 1/2] eal: add internal locks for timer lib into EAL

2019-07-04 Thread Burakov, Anatoly
On 04-Jul-19 10:09 AM, David Marchand wrote: On Tue, Jun 25, 2019 at 6:12 PM Anatoly Burakov wrote: Currently, timer library has a memory leak because there is no way to concurrently initialize/deinitialize shared memory because of race conditions [1]. Add a spinlock to the shared mem config

Re: [dpdk-dev] [PATCH 1/2] eal: add internal locks for timer lib into EAL

2019-07-04 Thread David Marchand
On Tue, Jun 25, 2019 at 6:12 PM Anatoly Burakov wrote: > Currently, timer library has a memory leak because there is no > way to concurrently initialize/deinitialize shared memory because > of race conditions [1]. > > Add a spinlock to the shared mem config to have a way to > exclusively initiali

Re: [dpdk-dev] [PATCH 1/2] eal: add internal locks for timer lib into EAL

2019-06-27 Thread Carrillo, Erik G
Hi Anatoly, > -Original Message- > From: Burakov, Anatoly > Sent: Tuesday, June 25, 2019 11:12 AM > To: dev@dpdk.org > Cc: Carrillo, Erik G > Subject: [PATCH 1/2] eal: add internal locks for timer lib into EAL > > Currently, timer library has a memory leak because there is no way to > co

[dpdk-dev] [PATCH 1/2] eal: add internal locks for timer lib into EAL

2019-06-25 Thread Anatoly Burakov
Currently, timer library has a memory leak because there is no way to concurrently initialize/deinitialize shared memory because of race conditions [1]. Add a spinlock to the shared mem config to have a way to exclusively initialize/deinitialize the timer library without any races. [1] See the fo