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 59CE9A0A02 for ; Wed, 5 May 2021 18:19:29 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1F3A640143; Wed, 5 May 2021 18:19:29 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by mails.dpdk.org (Postfix) with ESMTP id CEF9E40040 for ; Wed, 5 May 2021 18:19:27 +0200 (CEST) IronPort-SDR: zlO2vG1dGIscIIhohs9RltGu3ZUnlNWNHKFQ5XG1mew7XduvwlFgPah60oWKEzyN2MNTweOy24 hX5Sp/NGgxIw== X-IronPort-AV: E=McAfee;i="6200,9189,9975"; a="259525804" X-IronPort-AV: E=Sophos;i="5.82,276,1613462400"; d="scan'208";a="259525804" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 May 2021 09:19:26 -0700 IronPort-SDR: VhtQPph/iIWSOa7iXIkZRZw3Jj2nVMKhzeQqzT5BIzrW1/TRrBm6us9FJteX6enexc6Stnw2u6 0zPmep9NBI5w== X-IronPort-AV: E=Sophos;i="5.82,276,1613462400"; d="scan'208";a="433898057" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.194.51]) ([10.213.194.51]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 May 2021 09:19:24 -0700 To: "Templin (US), Fred L" , "users@dpdk.org" References: <62e934307738436988aefc7d292b7f28@boeing.com> From: Ferruh Yigit X-User: ferruhy Message-ID: <596d01d1-3472-4d47-8a1b-5037238baa66@intel.com> Date: Wed, 5 May 2021 17:19:21 +0100 MIME-Version: 1.0 In-Reply-To: <62e934307738436988aefc7d292b7f28@boeing.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] A simpler question - does DPDK run over virtual interfaces? 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 Sender: "users" On 4/13/2021 12:39 PM, Templin (US), Fred L wrote: > Let me backtrack and start by asking a simpler question - can DPDK run over > virtual interfaces such as a loopback? > It can, using DPDK virtual interfaces, like using 'af_packet' or 'pcap'. Like: "./build/app/dpdk-testpmd --vdev net_af_packet0,iface=lo --no-pci -- -i" I don't know about CORE vnode, but if it is seen as another Linux virtual interface, above should work same. This may work to test/check some functionality, but for performance you will need the physical interfaces. Btw, binding a physical interface to vfio driver is to enable driving it by DPDK, you don't need this step for Linux virtual interfaces. > Thanks - Fred > >> -----Original Message----- >> From: Templin (US), Fred L >> Sent: Monday, April 12, 2021 10:42 AM >> To: 'users@dpdk.org' >> Subject: Problems using DPDK within CORE emulations running on Ubuntu 18.04 VMs >> >> Hi, I am running Ubuntu 18.04 in a VM running on VirtualBox. I have built and >> installed DPDK-20.11 from sources and had no troubles building by following >> the Getting Started Guide for Linux instructions: >> >> http://doc.dpdk.org/guides/linux_gsg/intro.html >> >> Next, within the Ubuntu VM I run the CORE network emulator: >> >> https://www.nrl.navy.mil/Our-Work/Areas-of-Research/Information-Technology/NCS/CORE/ >> >> I have a simple two-node network setup with two CORE vnodes connected >> via a network switch, and verified that I can ping between the two nodes. >> Now, I want to experiment with the DPDK-20.11 "ip_fragmentation" and >> "ip_reassembly" example programs (which I was able to build successfully) >> but it appears that these example programs require ports to be mapped. >> >> So, I skipped ahead to Section 5 of the Getting Started Guide for Linux >> ("Linux Drivers") and tried to follow the instructions in Section 5.5. on >> "Binding and Unbinding Network Ports to/from the Kernel Modules" by >> typing commands into one of the CORE vnode shell windows. The text >> at the end of this message shows the commands I typed and the output >> I was shown in response. In particular, the "dpdk-devbind.py --status" >> script does not appear to show a usable map of my CORE vnode >> network interfaces, and attempts to bind were unsuccessful. >> >> Has anyone ever run DPDK out of a CORE vnode before and/or can >> you tell me what steps are needed to be able to bind CORE vnode >> interfaces so that they can be used by DPDK? Or, is DPDK simply >> incompatible with virtualization environments. >> >> Another question - can DPDK be run over loopback interfaces? >> >> Thanks - Fred >> >> --- >> >> Script started on 2021-04-12 09:54:19-0700 >> root@n1: pwd >> /home/fltemplin/src/DPDK/dpdk-20.11/usertools >> root@n1: ip link sho >> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >> 5: eth0@if6: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 >> link/ether 00:00:00:aa:00:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 >> root@n1: sudo modprobe vfio-pci >> root@n1: ip link sho >> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >> 5: eth0@if6: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 >> link/ether 00:00:00:aa:00:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 >> root@n1: ./dpdk-devbind.py --status >> >> Network devices using kernel driver >> =================================== >> 0000:00:03.0 '82540EM Gigabit Ethernet Controller 100e' if= drv=e1000 unused=vfio-pci >> 0000:00:08.0 '82540EM Gigabit Ethernet Controller 100e' if= drv=e1000 unused=vfio-pci >> >> No 'Baseband' devices detected >> ============================== >> >> No 'Crypto' devices detected >> ============================ >> >> No 'Eventdev' devices detected >> ============================== >> >> No 'Mempool' devices detected >> ============================= >> >> No 'Compress' devices detected >> ============================== >> >> No 'Misc (rawdev)' devices detected >> =================================== >> >> No 'Regex' devices detected >> =========================== >> root@n1: exit >> >> Script done on 2021-04-12 09:55:41-0700 >> >