From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <users-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 04107A034E for <public@inbox.dpdk.org>; Mon, 21 Feb 2022 20:03:04 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8F76C4068C; Mon, 21 Feb 2022 20:03:04 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 3D6F24013F for <users@dpdk.org>; Mon, 21 Feb 2022 20:03:03 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A152A5C003F; Mon, 21 Feb 2022 14:03:02 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 21 Feb 2022 14:03:02 -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=KMhtEGzZayc2eT 7obQK6kqMDueMIKvXVt2/R15SxSDA=; b=csZDhk9lpOrM0Z4+jrKtodM56jK8ae Qt2i1CSvxuNqhc9cwuM0xqgD5G+P2qsXiZ9QmMZwXNiApPq8WHNSvlBTZV5VCTnb cNquXhD3wgC9kbPQ5heiLy1oNHjM6fbYzN8n9UXVZUrheRziKykTH1rLJrWtpYKx IS1tBzpuOQmRFOR+NThiQ6Ae1t40Xet5KwxuZFsSK9t0ohNbvJj2nLWEbIVAQc0+ 7zDzDqiZh76LUB72a40w1Ixd9FdzMGRGKKICEcqsC1N6d4gQz2K9xGU1fc0VW2lk whG86hTOR/McMxOAhRzC7qZ95QpAuYkM4HoZVGPKNM6Ps2dxyzk4y3bA== 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=KMhtEGzZayc2eT7obQK6kqMDueMIKvXVt2/R15SxS DA=; b=BVMKVvk8C4LN/K7HvG/syZkJ1dVjup1mtslpcpo4bEnknsGUXk5rhsMJl KYlkzM6mJLxdwnhtQHb9MKw4o11a2h8ValMFGLdy6SrsnzNwhTiiwKHNh28UOVNz 2gYHDng4b+f9VLBsV0XYvEQwAW+UbDeV7vKntYsLU/pvs9UVGkCCp1xqzsBY6PW8 QhGlJGUboilFOWryxG64E61tf+ZjfH+HCx34YaQ768AmulhPdwrSZ+4tbmgHBn4C wLP6yQHCmFiCm4jGvzaze9Cl+UglUKSZGj8rS6GygU6DLLMsVJ4ulWfwLm+BnFLK wkWi/BxAAdzCo99PkOkTRZoVRB0hg== X-ME-Sender: <xms:5uETYoZWEWaW4pXzFnwMSzmPXb0oKAiLLOzDnTOJqRc4ukKGdcpvPQ> <xme:5uETYjZXnEikc3Yh8A7tzpb6Db0Op2Ll7-jhO0DVKkcUEdMdIxa2CVZzFbpTqzwU7 bvpHsXnCSCNzlxEkw> X-ME-Received: <xmr:5uETYi_-E5KgM1TguPJo9nVUMQUit99e8KicBHNPTtSg-iujiQf7FxPB9Z697yBNGGq-O3xRffUiBAZOXhcV_RF98A> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrkeeigdduudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfggfgtgesthfure dttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpeffvdffjeeuteelfeeile duudeugfetjeelveefkeejfeeigeehteffvdekfeegudenucffohhmrghinhepughpughk rdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: <xmx:5uETYirgGIPva8v-4_snWo7cE0y-IgZHUuMyTUkZ7VC4CBLZX8OSHw> <xmx:5uETYjry-HnBoPkdgrSEXqFjHfgz-jqarXjU_a6puy4tL61annQIpQ> <xmx:5uETYgTb_bLY_4S-8R-wnJp_Vy1OzdR55MVGLAKsd0yGiNFNupsQ6g> <xmx:5uETYsAG2PAORXYx_YXv4uyJn4mdGm3Ji5dKx9azuN58g_3as-HhoQ> Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 21 Feb 2022 14:03:01 -0500 (EST) From: Thomas Monjalon <thomas@monjalon.net> To: Aaron Lee <acl049@ucsd.edu> Cc: users@dpdk.org, asafp@nvidia.com Subject: Re: ConnectX5 Setup with DPDK Date: Mon, 21 Feb 2022 20:03:00 +0100 Message-ID: <3339719.uBEoKPz9u1@thomas> In-Reply-To: <1707201.A0I09U8b9p@thomas> References: <CAPd2kkVomsLKvzy98RnhRbUVtEosP3jZYqNX3s+sDhimLEXmMQ@mail.gmail.com> <1707201.A0I09U8b9p@thomas> 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 <users.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/users>, <mailto:users-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/users/> List-Post: <mailto:users@dpdk.org> List-Help: <mailto:users-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/users>, <mailto:users-request@dpdk.org?subject=subscribe> Errors-To: users-bounces@dpdk.org 21/02/2022 19:52, Thomas Monjalon: > 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 <mb_pool_0>: 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. If you want to check which hardware is supported by a PMD, you can use this command: usertools/dpdk-pmdinfo.py build/drivers/librte_net_mlx5.so PMD NAME: mlx5_eth PMD KMOD DEPENDENCIES: * ib_uverbs & mlx5_core & mlx5_ib PMD HW SUPPORT: Mellanox Technologies (15b3) : MT27700 Family [ConnectX-4] (1013) (All Subdevices) Mellanox Technologies (15b3) : MT27700 Family [ConnectX-4 Virtual Function] (1014) (All Subdevices) Mellanox Technologies (15b3) : MT27710 Family [ConnectX-4 Lx] (1015) (All Subdevices) Mellanox Technologies (15b3) : MT27710 Family [ConnectX-4 Lx Virtual Function] (1016) (All Subdevices) Mellanox Technologies (15b3) : MT27800 Family [ConnectX-5] (1017) (All Subdevices) Mellanox Technologies (15b3) : MT27800 Family [ConnectX-5 Virtual Function] (1018) (All Subdevices) Mellanox Technologies (15b3) : MT28800 Family [ConnectX-5 Ex] (1019) (All Subdevices) Mellanox Technologies (15b3) : MT28800 Family [ConnectX-5 Ex Virtual Function] (101a) (All Subdevices) Mellanox Technologies (15b3) : MT416842 BlueField integrated ConnectX-5 network controller (a2d2) (All Subdevices) Mellanox Technologies (15b3) : MT416842 BlueField multicore SoC family VF (a2d3) (All Subdevices) Mellanox Technologies (15b3) : MT28908 Family [ConnectX-6] (101b) (All Subdevices) Mellanox Technologies (15b3) : MT28908 Family [ConnectX-6 Virtual Function] (101c) (All Subdevices) Mellanox Technologies (15b3) : MT2892 Family [ConnectX-6 Dx] (101d) (All Subdevices) Mellanox Technologies (15b3) : ConnectX Family mlx5Gen Virtual Function (101e) (All Subdevices) Mellanox Technologies (15b3) : MT42822 BlueField-2 integrated ConnectX-6 Dx network controller (a2d6) (All Subdevices) Mellanox Technologies (15b3) : MT2894 Family [ConnectX-6 Lx] (101f) (All Subdevices) Mellanox Technologies (15b3) : MT2910 Family [ConnectX-7] (1021) (All Subdevices) Mellanox Technologies (15b3) : MT43244 BlueField-3 integrated ConnectX-7 network controller (a2dc) (All Subdevices) > Please tell me what drove you into the wrong direction, > because I really would like to improve the documentation & tools.