Re: [dpdk-dev] [PATCH] mem: fix deadlock on secondary allocation

2021-01-29 Thread Thomas Monjalon
29/01/2021 17:07, Burakov, Anatoly: > On 29-Jan-21 3:40 PM, Thomas Monjalon wrote: > > 29/01/2021 16:29, Anatoly Burakov: > >> Previous fix used `rte_malloc_heap_socket_is_external()` to check if the > >> heap was an external heap. However, that API is thread-safe, and when > >> we're inside the al

Re: [dpdk-dev] [PATCH] mem: fix deadlock on secondary allocation

2021-01-29 Thread Burakov, Anatoly
On 29-Jan-21 3:40 PM, Thomas Monjalon wrote: 29/01/2021 16:29, Anatoly Burakov: Previous fix used `rte_malloc_heap_socket_is_external()` to check if the heap was an external heap. However, that API is thread-safe, and when we're inside the allocation process, we're already write-locked, so calli

Re: [dpdk-dev] [PATCH] mem: fix deadlock on secondary allocation

2021-01-29 Thread Thomas Monjalon
29/01/2021 16:29, Anatoly Burakov: > Previous fix used `rte_malloc_heap_socket_is_external()` to check if the > heap was an external heap. However, that API is thread-safe, and when > we're inside the allocation process, we're already write-locked, so > calling `rte_malloc_heap_socket_is_external()

[dpdk-dev] [PATCH] mem: fix deadlock on secondary allocation

2021-01-29 Thread Anatoly Burakov
Previous fix used `rte_malloc_heap_socket_is_external()` to check if the heap was an external heap. However, that API is thread-safe, and when we're inside the allocation process, we're already write-locked, so calling `rte_malloc_heap_socket_is_external()` will result in a deadlock followed by a t