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 27B4745CFA for ; Wed, 13 Nov 2024 21:11:15 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0EE75406B8; Wed, 13 Nov 2024 21:11:15 +0100 (CET) Received: from mail-yw1-f176.google.com (mail-yw1-f176.google.com [209.85.128.176]) by mails.dpdk.org (Postfix) with ESMTP id 0E9BE40674 for ; Wed, 13 Nov 2024 21:11:13 +0100 (CET) Received: by mail-yw1-f176.google.com with SMTP id 00721157ae682-6ea8419a57eso79116897b3.1 for ; Wed, 13 Nov 2024 12:11:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cj-gy.20230601.gappssmtp.com; s=20230601; t=1731528672; x=1732133472; darn=dpdk.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=45qnBasR9zBJzIgmYLADY+wvdXmiULefx6u5K6HRkdY=; b=b+5ab19puALgcIdQ3ljSwyjjKQp2E25l/a8epE6cY/pyqEOabjCz7AEsQowfW487yE 2CRSF1Ub6+b6J78vn10Wfmpn/h3d2svKZCmmj/vwQh0TVxwH4MA73XI8EtzJ/OclsNVd thc8DknmR5+MxJoJ4y/WW/IvCgCWru7NNcdGGiuCl02VcGDVXXIMQHTzmfo/7UMtwUNt 13pitr4mqdH/tNGX4sqLc1Mo53DZxQ9wK+vn2GriBOLBvv8OMNRJ+nDCavgbNuydOaE/ uw2lvlfborS1Nwz+7Nx0LKya3zaJoGhnQEoH0c3ELWebMFckW7YyDRSI9PZyKnnZmM76 rziA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731528672; x=1732133472; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=45qnBasR9zBJzIgmYLADY+wvdXmiULefx6u5K6HRkdY=; b=GgvOdDVGy0WqnFqWEiYeDi3SjsMSgJz+Dq3YWnKgKCw8pQfDZMrydJe31ejW0k6roy PJHLfnVOy+5hplxfUGjpwcjWsErmWvJUa3IGBigKHxg2pPmLeXtVIfexCp/38jqBT90y nRaQKvV5Sv4kUr74sb8SHdAKwPU3u8SfqV67Q30MMpFDS8wbdFWDJ/rxyAJjaD4O9VSA scaZlSTXb60+jv4mTdI2YEvZy9mEh6VSNbSI1wCcmZwxr1aOfyM/zn6YgNhxyYpWvhsE cA4kuTMt8skxNtr0zZZjwmkhuJOwUGLU/icqRHNufmpKPbBgTNcV6yUBlAj+/w4BtITP Nghw== X-Gm-Message-State: AOJu0Yw3SCPyHc2ULdUswPrzUVLmGLV3rTVMi4lcMDuG0ZVGZmZ0gLKq J1avSqVCEH5TGfo8NwE0nHDTzlUfFEJ2FLqCA1HiI1hdE9LocUnkX66UeH+xpxrJ0uDdkFzMG5b uJmzzfIvDFxjGh4iwYjXqyXNNxbbGkzhuw1fbwjCIHbVTXXUimW4= X-Google-Smtp-Source: AGHT+IFsJGnqjLIq9UoDAhhjRWAIROOyWNC8t3CaICPwC6xm/KxV/fvCrA4KUKodl70a2KQhyKLbgx7wA/OV0bUO/W0= X-Received: by 2002:a05:690c:660c:b0:6e7:e68b:f883 with SMTP id 00721157ae682-6eaddfa3149mr229665457b3.39.1731528671793; Wed, 13 Nov 2024 12:11:11 -0800 (PST) MIME-Version: 1.0 From: CJ Sculti Date: Wed, 13 Nov 2024 15:10:58 -0500 Message-ID: Subject: DPDK with Mellanox ConnectX-5, complaining about mlx5_eth? To: users@dpdk.org Content-Type: multipart/alternative; boundary="00000000000066b1770626d0ef2a" 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 --00000000000066b1770626d0ef2a Content-Type: text/plain; charset="UTF-8" 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 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. --00000000000066b1770626d0ef2a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=
I've b= een 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 v= ersion my application uses, and compiled with support for mlx5 PMDs. Both 4= 0Gbps ports are up with link, and both are in Ethernet mode, not Infiniband= mode. However, I'm getting complaints when I start my application abou= t 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 applicatio= n fails to recognize them at all as valid DPDK devices. Anyone have any ide= as? 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=

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

0000:2b:00.0 'MT27800 Family [ConnectX= -5] 1017' if=3Denp43s0f0np0 drv=3Dmlx5_core unused=3Dvfio-pci=C2=A0

0000:2b:00.1 'MT27800 Family [Con= nectX-5] 1017' if=3Denp43s0f1np1 drv=3Dmlx5_core unused=3Dvfio-pci=C2= =A0


root@DDoSMitigation:~/anubis/engine/bin# ./anubis-engine=C2=A0

<= /span>

=C2=A0=C2=A0Electric 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: Prob= e PCI driver: mlx5_pci (15b3:1017) device: 0000:2b:00.1 (socket -1)<= /p>

mlx5_net: PF 0 doesn't have Verbs dev= ice matches PCI device 0000:2b:00.1, are kernel drivers loaded?

<= p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:n= ormal;font-variant-alternates:normal;font-size-adjust:none;font-kerning:aut= o;font-feature-settings:normal;font-stretch:normal;font-size:11px;line-heig= ht:normal;font-family:Menlo;color:rgb(0,0,0)">mlx5_common: Failed to load driver mlx5_eth

EAL: Requested device 0000:2b:00.1 = cannot be used

TELEMETRY: No legac= y 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 2= 3.11

USER1: Failed to reset link= fe0.


--00000000000066b1770626d0ef2a--