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 44BD445CFE for <public@inbox.dpdk.org>; Thu, 14 Nov 2024 00:00:56 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 36F1C402BC; Thu, 14 Nov 2024 00:00:56 +0100 (CET) Received: from mail-pl1-f180.google.com (mail-pl1-f180.google.com [209.85.214.180]) by mails.dpdk.org (Postfix) with ESMTP id 21B57402A1 for <users@dpdk.org>; Thu, 14 Nov 2024 00:00:55 +0100 (CET) Received: by mail-pl1-f180.google.com with SMTP id d9443c01a7336-20cceb8d8b4so9135455ad.1 for <users@dpdk.org>; Wed, 13 Nov 2024 15:00:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1731538854; x=1732143654; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=9njejMAOMEf4aGbzvkOknCnBt4XHFScA+0qcq/RCBRo=; b=uljxwSD5OJWE1PnpJuHMQMhEyPIt24cx6v8sMDuuFmEfsVC9DnIcMDvguvgEprZ/NO nKJO/FIBLRWHIild7IlhSA67vBdNuD6u+HEOcEeqBm5TxCGFiHx9237eUchEZy/BzvpD rAogZ/D6gzYfVtnnyZgiqneZv4Cc41G1anYNS3W+dOmG5dlDDydgTuhdX0tWEj2YHSUH 0i6EYeJImhkC0mNd3lkcBgxA7x87yP3bMP/CjQ8+UtGC8AOS0jS/jkFx5AO9MfxxqB+F GmMXyL2cfKxO8ZnOFcUyK2KZagyQZD5DwgcvmURfCp7b79BNOg7+Vz/lt3Nuy/3JDL5w QwjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731538854; x=1732143654; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9njejMAOMEf4aGbzvkOknCnBt4XHFScA+0qcq/RCBRo=; b=peYdG1Bi6Ro4yxaP+5GI+15oi92RqZ9ni0ttlelz1SMb8lisMXr8Zzud/7OB3ZIol+ 9o6mus4njxr/CYe80QfcsimyfZ3MboXvx4HHaEQSxnmDJrAETRq7vIiuof/MT7OJ2DWu BmngSb06877J5EewB3ohqqowFFxQbJCqfYex+SlJV7RXNo3bZRGRvmwQDCqRiwBhsyQp elLkAzrhN8dnoMljc5gi5oowIZDTaecda2m2WfUwQcussyAV8Q0EwPU1dqrtU72zwWKo w79MDzlWDWAUwHo/ynDGFGIh8ZkdAr8gD7q1KBozqf+bG7Hp0cfJAx3femBF2kDiPjeg VU0Q== X-Gm-Message-State: AOJu0YzORS32tUr5MZd5x2Kuwc8hff4rp7Woo8eC5LIzSPuuSb5LqanV LKF8aJTK4nyTaYZ0Rm+SwBC9etTfhSWLGD7eh9sS4fjWkqgTqsbkcExud8gVYNawt/SW+W7g3PY v X-Google-Smtp-Source: AGHT+IH1uFsMJJ6t9nf+z5GFgQy5ewcTioSjDc0QK24iyEQwmhAbal9VokXmEpY5wl+DPTNYWIjgGQ== X-Received: by 2002:a17:903:11c3:b0:20c:5ffe:3ef1 with SMTP id d9443c01a7336-211c0f897b9mr18521065ad.17.1731538854216; Wed, 13 Nov 2024 15:00:54 -0800 (PST) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-21177dde1adsm115127625ad.65.2024.11.13.15.00.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Nov 2024 15:00:53 -0800 (PST) Date: Wed, 13 Nov 2024 15:00:51 -0800 From: Stephen Hemminger <stephen@networkplumber.org> To: CJ Sculti <cj@cj.gy> Cc: users@dpdk.org Subject: Re: DPDK With Mellanox ConnectX-5 Message-ID: <20241113150051.7e655be7@hermes.local> In-Reply-To: <CANvjkS97X605fBJPy7nYi5DW8dYDzuqM4WgMdMKAvxxRVPN4Pg@mail.gmail.com> References: <CANvjkS97X605fBJPy7nYi5DW8dYDzuqM4WgMdMKAvxxRVPN4Pg@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Wed, 13 Nov 2024 15:06:17 -0500 CJ Sculti <cj@cj.gy> wrote: > I've been running my application for years on igb_uio with Intel NICs. I > recently replaced them with a Mellanox ConnectX-5 2x 40gbps NIC, updated > the DPDK version my application uses, and compiled with support for mlx5 > PMDs. Both 40Gbps ports are up with link, and both are in Ethernet mode, > not Infiniband mode. However, I'm getting complaints when I start my > application about trying to load 'mlx5_eth'? Both are bound to mlx5_core > driver at the moment. When I bind them to vfio-pci, or uio_pci_generic, my > application fails to recognize them at all as valid DPDK devices. Anyone > have any ideas? Also, strange that it only complains about one? I have them > configured in a bond on the kernel, as my application requires that. > > Network devices using kernel driver > > =================================== > > 0000:2b:00.0 'MT27800 Family [ConnectX-5] 1017' if=enp43s0f0np0 > drv=mlx5_core unused=vfio-pci > > 0000:2b:00.1 'MT27800 Family [ConnectX-5] 1017' if=enp43s0f1np1 > drv=mlx5_core unused=vfio-pci > > root@DDoSMitigation:~/anubis/engine/bin# ./anubis-engine > > > Electric Fence 2.2 Copyright (C) 1987-1999 Bruce Perens <bruce@perens.com> > > EAL: Detected CPU lcores: 12 > > EAL: Detected NUMA nodes: 1 > > EAL: Detected static linkage of DPDK > > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > > EAL: Selected IOVA mode 'VA' > > EAL: VFIO support initialized > > EAL: Probe PCI driver: mlx5_pci (15b3:1017) device: 0000:2b:00.0 (socket -1) > > EAL: Probe PCI driver: mlx5_pci (15b3:1017) device: 0000:2b:00.1 (socket -1) > > mlx5_net: PF 0 doesn't have Verbs device matches PCI device 0000:2b:00.1, > are kernel drivers loaded? > > mlx5_common: Failed to load driver mlx5_eth > > EAL: Requested device 0000:2b:00.1 cannot be used > > TELEMETRY: No legacy callbacks, legacy socket not created > > USER1: Anubis build master/. > > USER1: We will run on 12 logical cores. > > USER1: Enabled lcores not a power of 2! > > This could have performance issues. > > KNI: WARNING: KNI is deprecated and will be removed in DPDK 23.11 > > USER1: Failed to reset link fe0. MLX5 does not need or want vfio or igb_uio. https://doc.dpdk.org/guides/nics/mlx5.html