From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <users-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
by inbox.dpdk.org (Postfix) with ESMTP id 1B044A0524
for <public@inbox.dpdk.org>; Tue, 13 Apr 2021 13:39:20 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id 0A2DD1606E1;
Tue, 13 Apr 2021 13:39:20 +0200 (CEST)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net
[130.76.144.162])
by mails.dpdk.org (Postfix) with ESMTP id BED94160E6B
for <users@dpdk.org>; Tue, 13 Apr 2021 13:39:18 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id
13DBdG44017198; Tue, 13 Apr 2021 07:39:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com;
s=boeing-s1912; t=1618313957;
bh=Rv6kT/o8HQWvHRZHosvaVQGB5R6R3Y8Ej4DCzvH14bI=;
h=From:To:Subject:Date:From;
b=dnc6DEtFLz8/Vp1bjvtUmhiqOnTWFAWRX1rhoJvRvwMFvqCODJ7N2kuPmCAhfUIm2
utxoTUvPLXAW4pnQ+0qlL2DVIdyV2fAcNKxXlsum6Fz23Pp3hLAc6d+rZuO2xQvCND
4469jqu2BVhaJ+tXaCrnfThD1CpTQeB4ekdiSXKNM9Y5Jhc5kVDfmvvFIDkIVxza6K
w9GvZD2mKb2GfkE0++2Xp+YUIxt2u+9898+H1kEbJP1SfJQBlP74FEAHi2HuYPvWMC
SPSXE7vBwPbz/YeIlCBYStXxeLBvhT8awoiyimkxrRvar62MZJBSUE/dV8CzKfOzNY
g8uGlHobeksrA==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com
[144.115.66.112])
by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with
ESMTPS id 13DBd9Qs017151
(version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK)
for <users@dpdk.org>; Tue, 13 Apr 2021 07:39:09 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by
XCH16-07-10.nos.boeing.com (144.115.66.112) with Microsoft SMTP Server
(version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
15.1.2176.2; Tue, 13 Apr 2021 04:39:07 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by
XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id
15.01.2176.009; Tue, 13 Apr 2021 04:39:07 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "users@dpdk.org" <users@dpdk.org>
Thread-Topic: A simpler question - does DPDK run over virtual interfaces?
Thread-Index: AdcwWVsSsLezoQo7Sny/Jg9b63w1BQ==
Date: Tue, 13 Apr 2021 11:39:07 +0000
Message-ID: <62e934307738436988aefc7d292b7f28@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 0AF452190E84E049D5E4E8CA0016CF3FA4E895FF7097F7AD93C5AB81FE0D95662000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Subject: [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 <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
<mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
<mailto:users-request@dpdk.org?subject=subscribe>
Errors-To: users-bounces@dpdk.org
Sender: "users" <users-bounces@dpdk.org>
Let me backtrack and start by asking a simpler question - can DPDK run over
virtual interfaces such as a loopback?
Thanks - Fred
> -----Original Message-----
> From: Templin (US), Fred L
> Sent: Monday, April 12, 2021 10:42 AM
> To: 'users@dpdk.org' <users@dpdk.org>
> Subject: Problems using DPDK within CORE emulations running on Ubuntu 18.=
04 VMs
>=20
> 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 followi=
ng
> the Getting Started Guide for Linux instructions:
>=20
> http://doc.dpdk.org/guides/linux_gsg/intro.html
>=20
> Next, within the Ubuntu VM I run the CORE network emulator:
>=20
> https://www.nrl.navy.mil/Our-Work/Areas-of-Research/Information-Technolog=
y/NCS/CORE/
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> Another question - can DPDK be run over loopback interfaces?
>=20
> Thanks - Fred
>=20
> ---
>=20
> 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: <LOOPBACK,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue sta=
te 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: <LOOPBACK,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue sta=
te 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
>=20
> Network devices using kernel driver
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 0000:00:03.0 '82540EM Gigabit Ethernet Controller 100e' if=3D drv=3De1000=
unused=3Dvfio-pci
> 0000:00:08.0 '82540EM Gigabit Ethernet Controller 100e' if=3D drv=3De1000=
unused=3Dvfio-pci
>=20
> No 'Baseband' devices detected
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
>=20
> No 'Crypto' devices detected
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>=20
> No 'Eventdev' devices detected
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
>=20
> No 'Mempool' devices detected
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>=20
> No 'Compress' devices detected
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
>=20
> No 'Misc (rawdev)' devices detected
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> No 'Regex' devices detected
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> root@n1: exit
>=20
> Script done on 2021-04-12 09:55:41-0700
>=20