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 4874645CFB for ; Wed, 13 Nov 2024 22:43:47 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 09D12406B8; Wed, 13 Nov 2024 22:43:47 +0100 (CET) Received: from mail-yw1-f177.google.com (mail-yw1-f177.google.com [209.85.128.177]) by mails.dpdk.org (Postfix) with ESMTP id C6FCC40674 for ; Wed, 13 Nov 2024 22:43:45 +0100 (CET) Received: by mail-yw1-f177.google.com with SMTP id 00721157ae682-6ea15a72087so59884337b3.1 for ; Wed, 13 Nov 2024 13:43:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cj-gy.20230601.gappssmtp.com; s=20230601; t=1731534225; x=1732139025; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2v1adiZTcIwjKD6rqybV1HUxFG5t2Tzrau3Uf5uKYA0=; b=sw4P+d61yytCnpkWR8KdBmRMcconpm0emW4y9QENkvFl+rtntkdpkRMQ0MPr0YePpf +peuXshGRGvzaLUZgnZ8l6br6wRDr1+BYuIaDrIxpItp3ujpTXDQy75VEYtKJpTv/g4j 0YSRVVBFkiG7Iu0eMa3ZWWe4h2PYXW0FqK5Y+w3YMBPzHr2JwIfSzaqXBtpI4jzO5C7R o5SRE4vJ42GAaN1sOgORDG5ls/VILmrIqm64D5D/xLBbYGTqq0WFvVYb2SQjoneX+Vm/ cpm23WbEOCrFxreLnTXr9sY8uVQmkys1HGm+NUowz1fWU7qKvYQFdzCB7K2rbtczVSNP xBxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731534225; x=1732139025; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2v1adiZTcIwjKD6rqybV1HUxFG5t2Tzrau3Uf5uKYA0=; b=iSrKo19d0o6ITYTK7EyPAuhisTCbj+/xzxVX0+SJFfTBnZKeBRf9zg6LrvN3SH6q4b Se62TTYk4LrLZu1kcvrj6pOX8BaGLxHRMY00Pu6rlkzxvb2J/Qvp3Zv/xuDa6b2aLeoZ O2SKabJfIy3sSNyIexyHoX4Z4QOVXHbRza/5MciWS18o9gdJoyVl9JcMHRFbUyKdvPyE BJpSUKI5jimthhAu8+hVIFB9jCgEXa4ed5R0HKQjl89jteUKOSz1N3rvc68gXpyU6wdT 28mqnzpNPOVxBh6BgTmvNWnH8CFwQwnOZ0ZqP8mb96ldeCt/XAE7cTtcdnHeRxuV5M1F 6pFg== X-Gm-Message-State: AOJu0YwTrBQlnAk1ND18CvkJHy9iP/y8OOy0uflV70DCBNwhO9n1Df66 frzlfjfm6/a3G00K3NkXOSfSkr0LihaGQoDvL8jwLEQG9JykGHPmYter8+LfjtQhSAI/91452Qi BGB9WDLRRh1rVzSt/kz5rYYlbAu7FKrGve+wu5g== X-Google-Smtp-Source: AGHT+IH9gbKqm5G1/K4IB/5XIDCDwK4hUHFQdyVe+vJtoJteINmW9Sxad/Ee7bb45mbegnyLU/RlytHyVQ7tAqD+Nkk= X-Received: by 2002:a05:690c:6903:b0:6e3:14b0:ff86 with SMTP id 00721157ae682-6ecb345f54fmr49697737b3.27.1731534224517; Wed, 13 Nov 2024 13:43:44 -0800 (PST) MIME-Version: 1.0 References: <9487809.CDJkKcVGEf@thomas> In-Reply-To: <9487809.CDJkKcVGEf@thomas> From: CJ Sculti Date: Wed, 13 Nov 2024 16:43:33 -0500 Message-ID: Subject: Re: DPDK with Mellanox ConnectX-5, complaining about mlx5_eth? To: Thomas Monjalon Cc: users@dpdk.org, Dariusz Sosnowski Content-Type: multipart/alternative; boundary="0000000000005e85cd0626d23a5a" 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 --0000000000005e85cd0626d23a5a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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? On Wed, Nov 13, 2024 at 4:26=E2=80=AFPM Thomas Monjalon wrote: > 13/11/2024 21:10, CJ Sculti: > > 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, update= d > > the DPDK version my application uses, and compiled with support for mlx= 5 > > 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_cor= e > > 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. Anyon= e > > 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-drive= r > then > https://doc.dpdk.org/guides/platform/mlx5.html#design > > > > --0000000000005e85cd0626d23a5a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm not using vfio, I just bound inte= rfaces=C2=A0on there=C2=A0one time to test. Shouldn't I be able to just= use the default mlx5_core driver, without binding to uio_pci_generic?


On Wed, Nov 13, 2024 at 4:26=E2=80=AFPM Thomas Monjalon <thomas@monjalon.net> wrote:
13/11/2024 21:10, CJ S= culti:
> I've been running my application for years on igb_uio with Intel N= ICs. I
> recently replaced them with a Mellanox ConnectX-5 2x 40gbps NIC, updat= ed
> the DPDK version my application uses, and compiled with support for ml= x5
> PMDs. Both 40Gbps ports are up with link, and both are in Ethernet mod= e,
> 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. Anyo= ne
> 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/guide= s/linux_gsg/linux_drivers.html#bifurcated-driver
then
https://doc.dpdk.org/guides/platform/mlx5.html#= design



--0000000000005e85cd0626d23a5a--