From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) by dpdk.org (Postfix) with ESMTP id E883C1D392 for ; Fri, 15 Jun 2018 11:45:04 +0200 (CEST) X-Virus-Scanned: Proofpoint Essentials engine Received: from webmail.solarflare.com (uk.solarflare.com [193.34.186.16]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1-us4.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id A60D9280064; Fri, 15 Jun 2018 09:45:03 +0000 (UTC) Received: from [192.168.38.17] (91.220.146.112) by ukex01.SolarFlarecom.com (10.17.10.4) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Fri, 15 Jun 2018 10:44:59 +0100 To: Filip Janiszewski , References: <8e8c477b-066f-f909-d678-6623464b51c0@filipjaniszewski.com> From: Andrew Rybchenko Message-ID: Date: Fri, 15 Jun 2018 12:44:55 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="iso-8859-15"; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB X-Originating-IP: [91.220.146.112] X-ClientProxiedBy: ocex03.SolarFlarecom.com (10.20.40.36) To ukex01.SolarFlarecom.com (10.17.10.4) X-TM-AS-Product-Ver: SMEX-11.0.0.1191-8.100.1062-23908.003 X-TM-AS-Result: No--10.013400-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No X-MDID: 1529055904-EVnu7YHgeLJ2 Subject: Re: [dpdk-users] Correct setup of sfc X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 09:45:05 -0000 On 06/13/2018 10:14 PM, Filip Janiszewski wrote: > Hi Andrew, > > >> PCI devices of Solarflare NIC should be bound to vfio, uio-pci-generic or >> igb_uio (part of DPDK) module. In the case of Solarflare NICs, Linux >> driver is >> not required and not used in DPDK. >> >> So, you should load one of above modules (depending on your server >> IOMMU configuration), push already created interfaces down and rebind >> Solarflare PCI functions to the driver, something like: >> >> modprobe vfio-pci >> ip link set enp101s0f0 down >> ip link set enp101s0f1 down >> dpdk-devbind.py --bind=vfio-pci 0000:65:00.0 0000:65:00.1 >> >> The above assumes that dpdk-devbind.py script is in PATH. >> And start DPDK as you do before. >> > For some reason vfio-pci is refusing to bind the device: > > . > root usertools : ./dpdk-devbind.py --bind=vfio_pci 0000:65:00.0 0000:65:00.1 > Error: bind failed for 0000:65:00.0 - Cannot open > /sys/bus/pci/drivers/vfio_pci/bind > Error: bind failed for 0000:65:00.1 - Cannot open > /sys/bus/pci/drivers/vfio_pci/bind > . > > also: > > . > root usertools : echo 0000:65:00.0 > /sys/bus/pci/drivers/vfio-pci/bind > bash: echo: write error: No such device > . > > In the kernel command line I've included 'iommu=pt intel_iommu=on', but > still not working. Well I guess this is not a DPDK issue anymore. What does the following command shows? ./dpdk-devbind.py --status-dev net Is IOMMU (VT-d) enabled in BIOS/UEFI? You can check for files/symlinks in /sys/class/iommu. As an experiment I'd try uio-pci-generic as well. Also exact error logs from dmesg could be useful to understand what's going on. Andrew.