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 EF10D4300D for ; Tue, 8 Aug 2023 17:25:18 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 79BB343247; Tue, 8 Aug 2023 17:25:18 +0200 (CEST) Received: from mail-oi1-f176.google.com (mail-oi1-f176.google.com [209.85.167.176]) by mails.dpdk.org (Postfix) with ESMTP id 6C48140A87 for ; Tue, 8 Aug 2023 17:25:17 +0200 (CEST) Received: by mail-oi1-f176.google.com with SMTP id 5614622812f47-3a77ddccb2bso2584096b6e.0 for ; Tue, 08 Aug 2023 08:25:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691508316; x=1692113116; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=WXxLmMxAZxyj0s4qiSRdiogecxmEf1bEOilg8Xo1q8g=; b=XkZpvOI7mPrxcMkpc0tEp6qkuFBjgBvzYmkWpH2yzXc/r2ak6Wd5TMrNq1h/cfZoJh saZzLqG9KvTLrgDpekoRSGEufNYHKSUFWTPog2dKybagzzzIIcr1JL7iDcwrHTIY5efW zzsTATZoca/KagXrTgGmRNHPu2omfeUgew03218tUkayf6BtRYXFi1jTY6AC2mYBR3rR Dp0xzi9yVpvduREO04TzV373Picy3seLChgkL6lCVlK0tzlAG/5e1YMK6AkbKuX9sJzU bnmmWzeiU4UiBRITRHIbtVI/rAmU+vJ2uUVVt+uCdWRSkhHzHIAW9at1pLPcFHgjBkR9 B7Pw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691508316; x=1692113116; h=content-transfer-encoding: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=WXxLmMxAZxyj0s4qiSRdiogecxmEf1bEOilg8Xo1q8g=; b=MyBHdb6xWjYlju2HLm9VGzgV6KGLOPYM+nRAptpgUdUlnubutpLJbT5PA1kUf6dwMh Ci2YRuHHWTSD5OveIQZJ0+FyMPqCvYPy6zzBJlS2L1LRC9wGTt9TVStegHiR9hMwqL3S wv+3hK/Y6O0XIK3h6XRdnEc/AUHbKFIKwBbLzBlc+4Vvq/LcrK/b/Hgzdlu0EhHZUkWy 3/sIi53Ww9vYuAZ4gPIjvO8JX82PDGaCIsBsBMZlxNnRPV5Q1PrWWl27+EU67YHVJACh hadhDytnB9ds0H2U5hjLX4Ii3fjdm4S7Qf8Q5aUaS0gZIbG0UKmEdLeeDHQ42l5PvVk3 sxGw== X-Gm-Message-State: AOJu0YztV773x898g4MsVBz+zml5nLGUV7NtSwO+avSsthEg1Qjbzd/y Ky7Lgq5qAulIGT+nH4FIuivupx873S5Vg78isy9D30aAVVo= X-Google-Smtp-Source: AGHT+IGD7hbQsFpuxUEGKKg9xo2sAsjyo+cctLA6TZ3+huK7hQgPkK+BTVgMqCqtiOwVxKBGEAXjCw2I7NWpiN3tDc8= X-Received: by 2002:a05:6808:28d:b0:3a4:8e62:d9f1 with SMTP id z13-20020a056808028d00b003a48e62d9f1mr7483895oic.1.1691508316469; Tue, 08 Aug 2023 08:25:16 -0700 (PDT) MIME-Version: 1.0 References: <20230807124021.325b6d68@hermes.local> <20230807172645.3288f7e4@hermes.local> In-Reply-To: <20230807172645.3288f7e4@hermes.local> From: Alan Beadle Date: Tue, 8 Aug 2023 11:25:05 -0400 Message-ID: Subject: Re: Help Running Example To: Stephen Hemminger Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Thanks Stephen. It looks like my memory controller is in the same IOMMU group. I assume this means I won't be able to do this with this NIC? -Alan On Mon, Aug 7, 2023 at 8:26=E2=80=AFPM Stephen Hemminger wrote: > > On Mon, 7 Aug 2023 12:40:21 -0700 > Stephen Hemminger wrote: > > > On Sun, 6 Aug 2023 11:33:43 -0400 > > Alan Beadle wrote: > > > > > Hi, > > > > > > I need some help getting DPDK working. I am running Ubuntu 20.04 with > > > a modified Linux 5.4 kernel, but I have also tried the stock Ubuntu > > > 5.15 kernel with the same results. > > > > > > Here is my NIC info from lspci: > > > 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (3= ) > > > I219-LM (rev 09) > > > > > > I built and installed DPDK from source, and applied the following boo= t > > > flags: "intel_iommu=3Don iommu=3Dpt" > > > > > > After booting I did the following as root: > > > echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages > > > ifconfig enp0s31f6 down > > > dpdk-devbind.py --bind=3Dvfio-pci 0000:00:1f.6 > > > > > > All of this appeared to work. > > > > > > I tried running the "skeleton" example program and got the following = output: > > > sudo ./build/basicfwd > > > EAL: Detected CPU lcores: 16 > > > EAL: Detected NUMA nodes: 1 > > > EAL: Detected shared linkage of DPDK > > > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > > > EAL: Selected IOVA mode 'VA' > > > EAL: VFIO support initialized > > > EAL: 0000:00:1f.6 VFIO group is not viable! Not all devices in IOMMU > > > group bound to VFIO or unbound > > > EAL: Requested device 0000:00:1f.6 cannot be used > > > TELEMETRY: No legacy callbacks, legacy socket not created > > > EAL: Error - exiting with code: 1 > > > Cause: Error: number of ports must be even > > > > > > I'm not at all familiar with DPDK or VFIO. What might the problem be? > > > > > > -Alan > > > > IOMMU groups are when multiple PCI devices share the same channel > > in the IOMMU. The group is used to determine what mapping to use when > > device does DMA. Since this is a security thing, devices in same IOMMU > > group can not be shared between kernel and non-kernel usage. > > > > The IOMMU group is determined by wiring on the motherboard. > > Usually it is things like multiple Ethernet ports sharing the same grou= p. > > But can be much more confused. > > > > The only option is to unbind all devices in the group before using > > one with DPDK. > > More info on IOMMU groups is in kernel documentation: > https://www.kernel.org/doc/html/latest/driver-api/vfio.html > > and in this article > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/= html/virtualization_deployment_and_administration_guide/sect-iommu-deep-div= e