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

Andrew Rybchenko andrew.rybchenko at oktetlabs.ru
Mon Oct 10 10:02:12 CEST 2022


On 8/28/22 21:33, Slava Ovsiienko wrote:
>> -----Original Message-----
>> From: Dmitry Kozlyuk <dkozlyuk at nvidia.com>
>> Sent: Monday, August 8, 2022 12:43
>> To: dev at dpdk.org
>> Cc: Olivier Matz <olivier.matz at 6wind.com>; Andrew Rybchenko
>> <andrew.rybchenko at oktetlabs.ru>; stable at dpdk.org
>> Subject: [PATCH 1/2] mempool: make event callbacks process-private
>>
>> 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.
>>
>> Fixes: da2b9cb25e5f ("mempool: add event callbacks")
>> Cc: stable at dpdk.org
>>
>> Signed-off-by: Dmitry Kozlyuk <dkozlyuk at nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo at nvidia.com>

Reviewed-by: Andrew Rybchenko <andrew.rybchenko at oktetlabs.ru>



More information about the stable mailing list