From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id EAB94A00BE for ; Wed, 9 Mar 2022 20:49:12 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D73D7410E1; Wed, 9 Mar 2022 20:49:12 +0100 (CET) Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) by mails.dpdk.org (Postfix) with ESMTP id 90BE04013F; Wed, 9 Mar 2022 20:49:10 +0100 (CET) Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.1.2/8.16.1.2) with SMTP id 229Jdvn8000895; Wed, 9 Mar 2022 19:49:10 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding; s=pp1; bh=l+ThUFHyHvSqpt6+NVYxIlYGhWVp/S0Or3F2vNDf3yQ=; b=tWXgZ4EosCEkbKf7FAIjPwxDhXSOv+9N4UDiHfZHZ64u8fndcBQZmbqsqkJJt0wLB4Av 7QjZqKBE0LAZDQfEnR8Sj0nGPixhQxX7DpM0MOaFKhJTeAoZJHWfpf73DEUc2RBnWV19 WL9Y1aL9Z8hcaiqq79GFg/R93HsQ6UPsDssfBfgBNGyiAkVdh9vogJeXuJNBmBsqLUHd X24l7cIZvWEjuuuYQ/PQLIzqbr3Mci444+wlijvUwXZkJJmj5I2BIuIS7rQRXoV+XR6p h6qsbaJtuUh4TBaDA0UEiVsConYIryTueCcg4hl8pLTrN/JTrSdx7x66l9SxCo2lFcoY UA== Received: from ppma01wdc.us.ibm.com (fd.55.37a9.ip4.static.sl-reverse.com [169.55.85.253]) by mx0b-001b2d01.pphosted.com with ESMTP id 3ep0sdd6rc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 09 Mar 2022 19:49:09 +0000 Received: from pps.filterd (ppma01wdc.us.ibm.com [127.0.0.1]) by ppma01wdc.us.ibm.com (8.16.1.2/8.16.1.2) with SMTP id 229JRrVd018408; Wed, 9 Mar 2022 19:49:09 GMT Received: from b01cxnp23034.gho.pok.ibm.com (b01cxnp23034.gho.pok.ibm.com [9.57.198.29]) by ppma01wdc.us.ibm.com with ESMTP id 3ekyg9edwr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 09 Mar 2022 19:49:09 +0000 Received: from b01ledav003.gho.pok.ibm.com (b01ledav003.gho.pok.ibm.com [9.57.199.108]) by b01cxnp23034.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 229Jn8H531981916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 9 Mar 2022 19:49:08 GMT Received: from b01ledav003.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A260EB206B; Wed, 9 Mar 2022 19:49:08 +0000 (GMT) Received: from b01ledav003.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 24348B2064; Wed, 9 Mar 2022 19:49:08 +0000 (GMT) Received: from linux.vnet.ibm.com (unknown [9.40.193.248]) by b01ledav003.gho.pok.ibm.com (Postfix) with ESMTP; Wed, 9 Mar 2022 19:49:08 +0000 (GMT) From: Thinh Tran To: dev@dpdk.org Cc: drc@linux.vnet.ibm.com, viacheslavo@nvidia.com, rasland@nvidia.com, dkozlyuk@nvidia.com, Thinh Tran , stable@dpdk.org Subject: [PATCH v2] net/mlx5: fix CPU socket ID for Rx queue creation Date: Wed, 9 Mar 2022 14:49:00 -0500 Message-Id: <20220309194900.341944-1-thinhtr@linux.vnet.ibm.com> X-Mailer: git-send-email 2.27.0 In-Reply-To: <20220307225256.172328-1-thinhtr@linux.vnet.ibm.com> References: <20220307225256.172328-1-thinhtr@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 X-Proofpoint-ORIG-GUID: DkL44G11EjqY_skQ-U99pEfUmLARvGkV X-Proofpoint-GUID: DkL44G11EjqY_skQ-U99pEfUmLARvGkV X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.816,Hydra:6.0.425,FMLib:17.11.64.514 definitions=2022-03-09_07,2022-03-09_01,2022-02-23_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 malwarescore=0 adultscore=0 suspectscore=0 impostorscore=0 priorityscore=1501 phishscore=0 clxscore=1011 bulkscore=0 spamscore=0 mlxscore=0 lowpriorityscore=0 mlxlogscore=826 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2203090104 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org The default CPU socket ID was used while creating the Rx queue and this caused creation failure in case if hardware was not resided on the default socket. The patch sets the correct CPU socket ID for the mlx5_rxq_ctrl before calling the mlx5_rxq_create_devx_rq_resources() which eventually calls mlx5_devx_rq_create() with correct CPU socket ID. v2: change patch description, no code change Fixes: bc5bee028ebc ("net/mlx5: create drop queue using DevX") Cc: stable@dpdk.org Signed-off-by: Thinh Tran Reviewed-by: David Christensen --- drivers/net/mlx5/mlx5_devx.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/mlx5/mlx5_devx.c b/drivers/net/mlx5/mlx5_devx.c index af106bda50..5ab092a259 100644 --- a/drivers/net/mlx5/mlx5_devx.c +++ b/drivers/net/mlx5/mlx5_devx.c @@ -947,6 +947,8 @@ mlx5_rxq_devx_obj_drop_create(struct rte_eth_dev *dev) rte_errno = ENOMEM; goto error; } + /* set the CPU socket ID where the rxq_ctrl was allocated */ + rxq_ctrl->socket = socket_id; rxq_obj->rxq_ctrl = rxq_ctrl; rxq_ctrl->is_hairpin = false; rxq_ctrl->sh = priv->sh; -- 2.27.0