Re: [PATCH 1/2] mempool: make event callbacks process-private

2022-10-10 Thread Andrew Rybchenko
On 8/28/22 21:33, Slava Ovsiienko wrote: -Original Message- From: Dmitry Kozlyuk Sent: Monday, August 8, 2022 12:43 To: dev@dpdk.org Cc: Olivier Matz ; Andrew Rybchenko ; sta...@dpdk.org Subject: [PATCH 1/2] mempool: make event callbacks process-private Callbacks for mempool events

RE: [PATCH 1/2] mempool: make event callbacks process-private

2022-09-22 Thread Dmitry Kozlyuk
> From: Dmitry Kozlyuk > Sent: Monday, August 8, 2022 12:43 PM > To: dev@dpdk.org > Cc: Olivier Matz ; Andrew Rybchenko > ; sta...@dpdk.org > Subject: [PATCH 1/2] mempool: make event callbacks process-private > > Callbacks for mempool events were registered in a process-

RE: [PATCH 1/2] mempool: make event callbacks process-private

2022-08-28 Thread Slava Ovsiienko
> -Original Message- > From: Dmitry Kozlyuk > Sent: Monday, August 8, 2022 12:43 > To: dev@dpdk.org > Cc: Olivier Matz ; Andrew Rybchenko > ; sta...@dpdk.org > Subject: [PATCH 1/2] mempool: make event callbacks process-private > > Callbacks for mempool events w

[PATCH 1/2] mempool: make event callbacks process-private

2022-08-08 Thread Dmitry Kozlyuk
Callbacks for mempool events were registered in a process-shared tailq. This was inherently incorrect because the same function may be loaded to a different address in each process. Make the tailq process-private. Use the EAL tailq lock to reduce the number of different locks this module operates.