From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8B7FDC54E58 for ; Tue, 12 Mar 2024 08:57:04 +0000 (UTC) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 737B9402D8; Tue, 12 Mar 2024 09:57:03 +0100 (CET) Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) by mails.dpdk.org (Postfix) with ESMTP id 7D1B240687 for ; Mon, 11 Mar 2024 18:30:40 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 42BHUcKe022189; Mon, 11 Mar 2024 13:30:38 -0400 Received: from XCH16-11-07.nos.boeing.com (xch16-11-07.nos.boeing.com [144.115.66.34]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 42BHUQla021995 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Mon, 11 Mar 2024 13:30:26 -0400 Received: from XCH16-11-07.nos.boeing.com (144.115.66.34) by XCH16-11-07.nos.boeing.com (144.115.66.34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Mon, 11 Mar 2024 10:30:25 -0700 Received: from XCH16-11-07.nos.boeing.com ([fe80::f8bd:164d:61cc:d49a]) by XCH16-11-07.nos.boeing.com ([fe80::f8bd:164d:61cc:d49a%10]) with mapi id 15.01.2507.035; Mon, 11 Mar 2024 10:30:25 -0700 From: "Patel (US), Rajan P" To: "dev@dpdk.org" Subject: DPDK RDMA with Mellanox NIC and Ice Lake Xeon-D Thread-Topic: DPDK RDMA with Mellanox NIC and Ice Lake Xeon-D Thread-Index: Adpz2X/GTmz+SHyERPqXhQ5XvodsyQ== Date: Mon, 11 Mar 2024 17:30:25 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [144.115.204.6] x-tm-snts-smtp: E13DDD4BDE5F04EBBEE0C70623AFDD4B5D6D9342699A712E8F7679261022F3DB2000:8 Content-Type: multipart/alternative; boundary="_000_d22588ec4f794c668464ebe3cf305bb2drticom_" MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-Mailman-Approved-At: Tue, 12 Mar 2024 09:57:02 +0100 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --_000_d22588ec4f794c668464ebe3cf305bb2drticom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I see from your release notes that you have done testing of the Intel Xeon = D-17xx and D27xx line of CPUs with the Intel NIC. Has any work been done te= sting these CPUs with a Mellanox NIC? We are testing with this configuratio= n and running into issues - where as testing with Intel Scalable Processors= or previous generation Xeon D-15xx line works as expected. I was hoping to= get some insights as to configuration settings that may need to be applied= for this case if available. Is this a roadmap item that we can expect in a= future release? Thanks, Raj --_000_d22588ec4f794c668464ebe3cf305bb2drticom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

I see from your release notes that you have done tes= ting of the Intel Xeon D-17xx and D27xx line of CPUs with the Intel NIC. Ha= s any work been done testing these CPUs with a Mellanox NIC? We are testing= with this configuration and running into issues – where as testing with Intel Scalable Processors or pre= vious generation Xeon D-15xx line works as expected. I was hoping to get so= me insights as to configuration settings that may need to be applied for th= is case if available. Is this a roadmap item that we can expect in a future release?

Thanks,

Raj

--_000_d22588ec4f794c668464ebe3cf305bb2drticom_--