From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 36BD31BE35 for ; Thu, 5 Jul 2018 17:41:50 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Jul 2018 08:41:48 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,312,1526367600"; d="scan'208";a="54672380" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by orsmga008.jf.intel.com with ESMTP; 05 Jul 2018 08:41:48 -0700 Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 5 Jul 2018 08:41:47 -0700 Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.220]) by fmsmsx120.amr.corp.intel.com ([10.18.124.208]) with mapi id 14.03.0319.002; Thu, 5 Jul 2018 08:41:47 -0700 From: "Wiles, Keith" To: Bala Sankaran CC: "users@dpdk.org" , Aaron Conole Thread-Topic: [dpdk-users] Traffic doesn't forward on virtual devices Thread-Index: oQTMFRAawVHbwy4YZZ9aWPlHFRqacrwmn7/y4mqY1QA= Date: Thu, 5 Jul 2018 15:41:46 +0000 Message-ID: References: <1882345510.2557424.1530213493803.JavaMail.zimbra@redhat.com> <329369015.3963546.1530802400841.JavaMail.zimbra@redhat.com> In-Reply-To: <329369015.3963546.1530802400841.JavaMail.zimbra@redhat.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.136.45] Content-Type: text/plain; charset="us-ascii" Content-ID: <78B9F2231ED564468392B14F9F0E7E4A@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] Traffic doesn't forward on virtual devices 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: Thu, 05 Jul 2018 15:41:50 -0000 > On Jul 5, 2018, at 9:53 AM, Bala Sankaran wrote: >=20 > Greetings, >=20 > I am currently using dpdk version 17.11.2. I see that there are a few oth= er=20 > revisions in 17.11.3, followed by the latest stable version of 18.02.2.=20 >=20 > Based on the issues I have faced so far (see Original=20 > Message below), would you suggest that I go for=20 > another version? If yes, which one? In essence, my question is, would=20 > resorting to a different version of dpdk solve my current issue of=20 > virtqueue id being invalid?=20 >=20 > Any help is much appreciated. >>From a support perspective using the latest version 18.05 or the long term = supported version 17.11.3 is easier for most to help. I would pick the late= st release 18.05 myself. As for fixing this problem I do not know. You can = look into the MAINTAINERS file and find the maintainers of area(s) and incl= ude them in the CC line on your questions as sometimes they miss the emails= as the volume can be high at times. >=20 > Thanks >=20 > ----- Original Message ----- >> From: "Bala Sankaran" >> To: users@dpdk.org >> Cc: "Aaron Conole" >> Sent: Thursday, June 28, 2018 3:18:13 PM >> Subject: Traffic doesn't forward on virtual devices >>=20 >>=20 >> Hello team, >>=20 >> I am working on a project to do PVP tests on dpdk. As a first step, I wo= uld >> like to get traffic flow between tap devices. I'm in process of setting = up >> the architecture, in which I've used testpmd to forward traffic between = two >> virtual devices(tap and vhost users) over a bridge. >>=20 >> While I'm at it, I've identified that the internal dev_attached flag nev= er >> gets set to 1 from the rte_eth_vhost.c file. I've tried to manually set = it >> to 1 in the start routine, but I just see that the queue index being >> referenced is out of range. >>=20 >> I'm not sure how to proceed. Has anyone had luck using testpmd to >> communicate with vhost-user devices? If yes, any hints on a workaround? >>=20 >> Here's how I configured my setup after installing dpdk and openvswitch: >>=20 >> 1. To start ovs-ctl: >> /usr/local/share/openvswitch/scripts/ovs-ctl start >>=20 >> 2. Setup hugepages: >> echo '2048' > /proc/sys/vm/nr_hugepages >>=20 >> 3. Add a new network namespace: >> ip netns add ns1 >>=20 >> 4. Add and set a bridge: >> ovs-vsctl add-br dpdkbr0 -- set Bridge dpdkbr0 datapath_type=3Dnetdev >> options:vhost-server-path=3D/usr/local/var/run/openvswitch/vhu0 >> ovs-vsctl show >>=20 >> 5. Add a vhost user to the bridge created: >> ovs-vsctl add-port dpdkbr0 vhu0 -- set Interface vhu0 >> type=3Ddpdkvhostuserclient >>=20 >> 6. Execute bash on the network namespace: >> ip netns exec ns1 bash >>=20 >> 7. Use testpmd and connect the namespaces: >> testpmd --socket-mem=3D512 >> --vdev=3D'eth_vhost0,iface=3D/usr/local/var/run/openvswitch/vhu0,queues= =3D1' >> --vdev=3D'net_tap0,iface=3Dtap0' --file-prefix page0 -- -i >>=20 >>=20 >> I repeated steps 3 - 7 for another network namespace on the same bridge. >> Following this, in fresh terminals, I assigned IP addresses to the tap >> devices created and tried pinging them. From port statistics, >> I identified the above mentioned issue with the dev_attached and queue >> statistics. >>=20 >> I would greatly appreciate any help from your end. >>=20 >> Thanks. >>=20 >> ------------------------------------------------- >> Bala Sankaran >> Networking Services Intern >> Red Hat Inc ., >>=20 > ------------------------------------------------- > Bala Sankaran > Networking Services Intern Regards, Keith