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 E3969A034E for ; Mon, 21 Feb 2022 19:52:45 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D926D4068C; Mon, 21 Feb 2022 19:52:45 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 4A7AF4013F for ; Mon, 21 Feb 2022 19:52:44 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B36955C021A; Mon, 21 Feb 2022 13:52:43 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 21 Feb 2022 13:52:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; bh=79LScxcioDZ7xb vzdor44Y9UTGNWMGQ6ey61m9pEULY=; b=JZFQkmMsFlmX5Pw6iLgebrenx6E91Q nh1CbKwytFhiSv98xTkrmd5vOB7cEzovh4ekCKHZ6sDa6Aeh0EAG1nQGHjlpQ1ZK OzBzNPnWgNJYNZuPybdIeHha1l0yXyjECK6IYHSEBnnufStrEGNNNhq6UywFC952 YbeHCOwJRoxbuh0IAWYvaEWLfYfAfpJShhnxqulgjcrB07CH7n2UHrjX7e9Je2gs 2U5Y7KsQS4Fu/OXPLhsNGbv4/YD5aw2JBOzIvPv/3IBqBfSgvH33gqOmEZMUtc5a Fr5pwRPNMAyktXwmSwddaIpqes253Bt+EpfiRBSLRpLRNtkoLJsuPzyA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=79LScxcioDZ7xbvzdor44Y9UTGNWMGQ6ey61m9pEU LY=; b=RjnZUvspHxL0E32cio5qGSGqJ1RavAzPDjVT3dVlbNq7StJCteB0uuuN6 JJZgkXFccvcZrYRM8FDJOqOPMkEjgFTWQz4EK4lBQlS6cZAp1eyUCo7bQZ1PW6+r RUj3OK6UXJ8Ik++lSJkYGyn/xko+oHqbi2WxpM5BOzDHnRNJ4oAZY+H6bb4DhC0M 3LTo4916LLS4SOR/tcSbq2rqzSDa+xkTrhc5B0MFI8F+8ofmk9WTR/fLuT44o2Ab UeLLVgVaJOjZbVYsQMIPQg3EfIY8Mxf8sQTDIIYuaOssza/fi3UYgPrLjGCu5043 qxoY4XaPAvDoFr9SR/RCfBmOBRKlg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrkeeigdduudeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfggfgtgesthfure dttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpeffvdffjeeuteelfeeile duudeugfetjeelveefkeejfeeigeehteffvdekfeegudenucffohhmrghinhepughpughk rdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 21 Feb 2022 13:52:42 -0500 (EST) From: Thomas Monjalon To: Aaron Lee Cc: users@dpdk.org, asafp@nvidia.com Subject: Re: ConnectX5 Setup with DPDK Date: Mon, 21 Feb 2022 19:52:41 +0100 Message-ID: <1707201.A0I09U8b9p@thomas> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org 18/02/2022 22:12, Aaron Lee: > Hello, > > I'm trying to get my ConnectX5 NIC working with DPDK v21.11 but I'm > wondering if the card I have simply isn't compatible. I first noticed that > the model I was given is MCX515A-CCA_Ax_Bx. Below are some of the error > logs when running dpdk-pdump. When testing a NIC, it is more convenient to use dpdk-testpmd. > EAL: Detected CPU lcores: 80 > EAL: Detected NUMA nodes: 2 > EAL: Detected static linkage of DPDK > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_383403_1ac7441297c92 > EAL: failed to send to (/var/run/dpdk/rte/mp_socket) due to No such file or > directory > EAL: Fail to send request /var/run/dpdk/rte/mp_socket:bus_vdev_mp > vdev_scan(): Failed to request vdev from primary > EAL: Selected IOVA mode 'PA' > EAL: failed to send to (/var/run/dpdk/rte/mp_socket) due to No such file or > directory > EAL: Fail to send request /var/run/dpdk/rte/mp_socket:eal_vfio_mp_sync > EAL: Cannot request default VFIO container fd > EAL: VFIO support could not be initialized > EAL: Probe PCI driver: mlx5_pci (15b3:1017) device: 0000:af:00.0 (socket 1) > EAL: failed to send to (/var/run/dpdk/rte/mp_socket) due to No such file or > directory > EAL: Fail to send request /var/run/dpdk/rte/mp_socket:common_mlx5_mp > mlx5_common: port 0 request to primary process failed > mlx5_net: probe of PCI device 0000:af:00.0 aborted after encountering an > error: No such file or directory > mlx5_common: Failed to load driver mlx5_eth > EAL: Requested device 0000:af:00.0 cannot be used > EAL: Error - exiting with code: 1 > Cause: No Ethernet ports - bye >From this log, we miss the previous steps before running the application. Please check these simple steps: - install rdma-core - build dpdk (meson build && ninja -C build) - reserve hugepages (usertools/dpdk-hugepages.py -r 1G) - run testpmd (echo show port summary all | build/app/dpdk-testpmd --in-memory -- -i) EAL: Detected CPU lcores: 10 EAL: Detected NUMA nodes: 1 EAL: Detected static linkage of DPDK EAL: Selected IOVA mode 'PA' EAL: Probe PCI driver: mlx5_pci (15b3:101f) device: 0000:08:00.0 (socket 0) Interactive-mode selected testpmd: create a new mbuf pool : n=219456, size=2176, socket=0 testpmd: preferred mempool ops selected: ring_mp_mc Configuring Port 0 (socket 0) Port 0: 0C:42:A1:D6:E0:00 Checking link statuses... Done testpmd> show port summary all Number of available ports: 1 Port MAC Address Name Driver Status Link 0 0C:42:A1:D6:E0:00 08:00.0 mlx5_pci up 25 Gbps > I noticed that the pci id of the card I was given is 15b3:1017 as below. > This sort of indicates to me that the PMD driver isn't supported on this > card. This card is well supported and even officially tested with DPDK 21.11, as you can see in the release notes: https://doc.dpdk.org/guides/rel_notes/release_21_11.html#tested-platforms > af:00.0 Ethernet controller [0200]: Mellanox Technologies MT27800 Family > [ConnectX-5] [15b3:1017] > > I'd appreciate it if someone has gotten this card to work with DPDK to > point me in the right direction or if my suspicions were correct that this > card doesn't work with the PMD. Please tell me what drove you into the wrong direction, because I really would like to improve the documentation & tools.