[dpdk-dev] [PATCH v2] net/qede: fix alloc from socket 0

Ferruh Yigit ferruh.yigit at intel.com
Wed Mar 7 14:17:50 CET 2018


On 2/26/2018 6:38 PM, Patil, Harish wrote:
> -----Original Message-----
> From: Pascal Mazon <pascal.mazon at 6wind.com>
> Date: Monday, February 26, 2018 at 12:01 AM
> To: "dev at dpdk.org" <dev at dpdk.org>, "Mody, Rasesh"
> <Rasesh.Mody at cavium.com>, Harish Patil <Harish.Patil at cavium.com>, "Shaikh,
> Shahed" <Shahed.Shaikh at cavium.com>
> Cc: "pascal.mazon at 6wind.com" <pascal.mazon at 6wind.com>, "stable at dpdk.org"
> <stable at 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: stable at dpdk.org
>>
>> Signed-off-by: Pascal Mazon <pascal.mazon at 6wind.com>
>> Acked-by: Harish Patil <harish.patil at cavium.com>

> Acked-by: Harish Patil <harish.patil at cavium.com>

Applied to dpdk-next-net/master, thanks.


More information about the dev mailing list