On 2/26/2018 6:38 PM, Patil, Harish wrote: > -----Original Message----- > From: Pascal Mazon <pascal.ma...@6wind.com> > Date: Monday, February 26, 2018 at 12:01 AM > To: "email@example.com" <firstname.lastname@example.org>, "Mody, Rasesh" > <rasesh.m...@cavium.com>, Harish Patil <harish.pa...@cavium.com>, "Shaikh, > Shahed" <shahed.sha...@cavium.com> > Cc: "pascal.ma...@6wind.com" <pascal.ma...@6wind.com>, "sta...@dpdk.org" > <sta...@dpdk.org> > Subject: [PATCH v2] net/qede: fix alloc from socket 0 > >> In case osal_dma_alloc_coherent() or osal_dma_alloc_coherent_aligned() are >> called from a management thread, core_id turn out to be LCORE_ID_ANY, and >> the resulting socket for alloc will be socket 0. >> >> This is not desirable when using a NIC from socket 1 which might very >> likely be configured to use memory from that socket only. >> In that case, allocation will fail. >> >> To address this, use master lcore instead when called from mgmt thread. >> The associated socket should have memory available. >> >> Fixes: ec94dbc57362 ("qede: add base driver") >> Cc: sta...@dpdk.org >> >> Signed-off-by: Pascal Mazon <pascal.ma...@6wind.com> >> Acked-by: Harish Patil <harish.pa...@cavium.com>
> Acked-by: Harish Patil <harish.pa...@cavium.com> Applied to dpdk-next-net/master, thanks.