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 709EC45CFB for ; Wed, 13 Nov 2024 23:43:05 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 41B10406B8; Wed, 13 Nov 2024 23:43:05 +0100 (CET) Received: from fout-a5-smtp.messagingengine.com (fout-a5-smtp.messagingengine.com [103.168.172.148]) by mails.dpdk.org (Postfix) with ESMTP id DC94440674 for ; Wed, 13 Nov 2024 23:43:03 +0100 (CET) Received: from phl-compute-07.internal (phl-compute-07.phl.internal [10.202.2.47]) by mailfout.phl.internal (Postfix) with ESMTP id 5DCC613801CB; Wed, 13 Nov 2024 17:43:03 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-07.internal (MEProxy); Wed, 13 Nov 2024 17:43:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1731537783; x=1731624183; bh=n8kBUfcXvY47bBBmMgb7KCImSht7Ukg3/DyyS9/hP4k=; b= zHhxlmZzcP84PkBOcY7LVbiaSipxnJSfeuTntTUcBlxVV8xETE4cB0Tq8jC/yBK2 GI6jn6nrQBXjxDEAIA+Y7cLZmnAdPYCdzjuxnNr/ErHyrTEJqiUs7hdRp/ynqSdS adE72JvFMvAPkTBu0IT0KGT3YGTeBxPMTP/kTbgRgKsYUs8e7neMHypfGVlLjP1q zxIGfFF6plziz9KEGnO9Kay/mIkebhn20Fdj6eoQmUwSct/Ee9pS3CIrVXbcv51/ o875YOfOVpPea3W91oFzITOH56ZM2dftCGTWTUk4l7UFymDhy7XTpf1JoaE+rJyn yxF5T6IAogBz18CLfp66ag== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1731537783; x= 1731624183; bh=n8kBUfcXvY47bBBmMgb7KCImSht7Ukg3/DyyS9/hP4k=; b=Q P7ly86/5kpI4Z7SLA1ZjlsRqNRXWBzNHVZvZRctnsCQefVWAiF5eZDXu125/J2AF 8+rXKz6PaLxgvNo/AWHg3FmBrfhxsrf6/mPLHetL6OrUHqbE0iqlSaotooFYwviC rczlVCjOUOakMv7DQ7gUVKqUcv0XsG6lRTbncmrShOxtJUhOOFcx5snbC8PtClNp vxMmtfWDqHhnIt4w3WvkiUljYwrLExHn0GP3OUS6vSGO7umSayVIiXP4iK1qOb7K oUTxYLdj8mjQAbOefO8aekDqcidXjBbtVOGgtk6a0MEUqC0bc/tLauhdoWRwHqI5 KqHGyE+VdD+26Gm/59J8A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrvddugddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefhvfevufffkfgjfhgggfgtsehtqhertddttdejnecu hfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlh honhdrnhgvtheqnecuggftrfgrthhtvghrnhepffdtuefhhedvkeelleevffdvlefhleeh vdegtddvvdduueeivedtgfejvddugeefnecuffhomhgrihhnpeguphgukhdrohhrghenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgr shesmhhonhhjrghlohhnrdhnvghtpdhnsggprhgtphhtthhopeefpdhmohguvgepshhmth hpohhuthdprhgtphhtthhopegtjhestghjrdhghidprhgtphhtthhopehushgvrhhssegu phgukhdrohhrghdprhgtphhtthhopegushhoshhnohifshhkihesnhhvihguihgrrdgtoh hm X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 13 Nov 2024 17:43:02 -0500 (EST) From: Thomas Monjalon To: CJ Sculti Cc: users@dpdk.org, Dariusz Sosnowski Subject: Re: DPDK with Mellanox ConnectX-5, complaining about mlx5_eth? Date: Wed, 13 Nov 2024 23:43:00 +0100 Message-ID: <6119651.MhkbZ0Pkbq@thomas> In-Reply-To: References: <9487809.CDJkKcVGEf@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" 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 13/11/2024 22:43, CJ Sculti: > I'm not using vfio, I just bound interfaces on there one time to test. > Shouldn't I be able to just use the default mlx5_core driver, without > binding to uio_pci_generic? Yes you must not bind to anything else than mlx5 kernel driver. Please try to follow the documentation and tell us what you find. > On Wed, Nov 13, 2024 at 4:26=E2=80=AFPM Thomas Monjalon wrote: >=20 > > 13/11/2024 21:10, CJ Sculti: > > > I've been running my application for years on igb_uio with Intel NICs= =2E I > > > recently replaced them with a Mellanox ConnectX-5 2x 40gbps NIC, upda= ted > > > the DPDK version my application uses, and compiled with support for m= lx5 > > > PMDs. Both 40Gbps ports are up with link, and both are in Ethernet mo= de, > > > not Infiniband mode. However, I'm getting complaints when I start my > > > application about trying to load 'mlx5_eth'? Both are bound to mlx5_c= ore > > > driver at the moment. When I bind them to vfio-pci, or uio_pci_generi= c, > > my > > > application fails to recognize them at all as valid DPDK devices. Any= one > > > 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. > > > > You must not bind mlx5 devices with VFIO. > > I recommend reading documentation. > > You can start here: > > https://doc.dpdk.org/guides/linux_gsg/linux_drivers.html#bifurcated-dri= ver > > then > > https://doc.dpdk.org/guides/platform/mlx5.html#design