Re: [dpdk-dev] [RFC] mem: add atomic lookup-and-reserve/free memzone API

2020-05-06 Thread Burakov, Anatoly
On 05-May-20 4:01 PM, Bruce Richardson wrote: On Tue, May 05, 2020 at 02:24:07PM +, Anatoly Burakov wrote: Currently, in order to perform a memzone lookup and create/free the memzone, the user has to call two API's, creating a race condition. This is particularly destructive for memzone_free

Re: [dpdk-dev] [RFC] mem: add atomic lookup-and-reserve/free memzone API

2020-05-05 Thread Bruce Richardson
On Tue, May 05, 2020 at 02:24:07PM +, Anatoly Burakov wrote: > Currently, in order to perform a memzone lookup and create/free > the memzone, the user has to call two API's, creating a race > condition. This is particularly destructive for memzone_free call > because the reference provided to m

[dpdk-dev] [RFC] mem: add atomic lookup-and-reserve/free memzone API

2020-05-05 Thread Anatoly Burakov
Currently, in order to perform a memzone lookup and create/free the memzone, the user has to call two API's, creating a race condition. This is particularly destructive for memzone_free call because the reference provided to memzone_free at the time of call may be stale or refer to a different memz