patch with suggestions above.
Regards,
Thinh
-Original Message-
From: Raslan Darawsheh
Sent: Tuesday, March 8, 2022 14:25
To: Dmitry Kozlyuk
Cc: Thinh Tran ; dev@dpdk.org;
d...@linux.vnet.ibm.com
Subject: RE: [PATCH] net/mlx5: set correct CPU socket ID for mlx5_rxq_ctrl
-Original Message-
2022 14:25
> To: Dmitry Kozlyuk
> Cc: Thinh Tran ; dev@dpdk.org;
> d...@linux.vnet.ibm.com
> Subject: RE: [PATCH] net/mlx5: set correct CPU socket ID for mlx5_rxq_ctrl
>
>
> > -Original Message-
> > From: Dmitry Kozlyuk
> > Sent: Tuesday, Mar
> -Original Message-
> From: Dmitry Kozlyuk
> Sent: Tuesday, March 8, 2022 2:23 PM
> To: Raslan Darawsheh
> Cc: Thinh Tran ; dev@dpdk.org;
> d...@linux.vnet.ibm.com
> Subject: Re: [PATCH] net/mlx5: set correct CPU socket ID for mlx5_rxq_ctrl
>
> Hi Raslan,
&g
Hi Raslan,
> Missing:
> Fixes tag:
>
> Fixes: 5ceb3a02b000 ("net/mlx5: move Rx queue DevX resource")
> Cc: xuemi...@nvidia.com
I believe the bug originates from my earlier commit, not Xueming's one:
Fixes: bc5bee028ebc ("net/mlx5: create drop queue using DevX")
Hi Thinh,
> -Original Message-
> From: Thinh Tran
> Sent: Tuesday, March 8, 2022 12:53 AM
> To: dev@dpdk.org
> Cc: d...@linux.vnet.ibm.com; Thinh Tran
> Subject: [PATCH] net/mlx5: set correct CPU socket ID for mlx5_rxq_ctrl
>
This is a fix, so it's better to
From: Thinh Tran
> I hit a failure during ports drop queue RQ creation when my adapters are on
> CPU
> socket ID 1 instead of socket ID 0:
>
> EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0020:01:00.0 (socket 1)
> EAL: set_mempolicy failed: Invalid argument
> mlx5_common: Failed to al
I hit a failure during ports drop queue RQ creation when my adapters
are on CPU socket ID 1 instead of socket ID 0:
EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0020:01:00.0 (socket 1)
EAL: set_mempolicy failed: Invalid argument
mlx5_common: Failed to allocate memory for RQ.
mlx5_net: P
7 matches
Mail list logo