Re: [dpdk-dev] [PATCH] net/memif: allocate socket hash on any NUMA socket

On 10/4/2021 1:02 PM, Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco) wrote: > > >> On 9/28/2021 2:51 PM, Junxiao Shi wrote: >>> Previously, memif socket hash is always allocated on NUMA socket 0. >>> If the application is entirely running on another NUMA socket and EAL >>> --socket-li

Re: [dpdk-dev] [PATCH] net/memif: allocate socket hash on any NUMA socket

> On 9/28/2021 2:51 PM, Junxiao Shi wrote: > > Previously, memif socket hash is always allocated on NUMA socket 0. > > If the application is entirely running on another NUMA socket and EAL > > --socket-limit prevents memory allocation on NUMA socket 0, memif > > creation fails with "HASH: memory

Re: [dpdk-dev] [PATCH] net/memif: allocate socket hash on any NUMA socket

On 9/28/2021 2:51 PM, Junxiao Shi wrote: > Previously, memif socket hash is always allocated on NUMA socket 0. > If the application is entirely running on another NUMA socket and EAL > --socket-limit prevents memory allocation on NUMA socket 0, memif > creation fails with "HASH: memory allocation f

[dpdk-dev] [PATCH] net/memif: allocate socket hash on any NUMA socket

Previously, memif socket hash is always allocated on NUMA socket 0. If the application is entirely running on another NUMA socket and EAL --socket-limit prevents memory allocation on NUMA socket 0, memif creation fails with "HASH: memory allocation failed" error. This patch allows allocating memif