From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 1486F5F3B; Tue, 10 Jul 2018 10:20:34 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jul 2018 01:20:34 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,333,1526367600"; d="scan'208";a="65758479" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by orsmga003.jf.intel.com with ESMTP; 10 Jul 2018 01:20:32 -0700 Received: from irsmsx106.ger.corp.intel.com ([169.254.8.211]) by IRSMSX102.ger.corp.intel.com ([169.254.2.110]) with mapi id 14.03.0319.002; Tue, 10 Jul 2018 09:20:32 +0100 From: "Loftus, Ciara" To: Aaron Conole , Bala Sankaran CC: "Wiles, Keith" , "users@dpdk.org" , "dev@dpdk.org" , Maxime Coquelin , "Stokes, Ian" Thread-Topic: [dpdk-users] Traffic doesn't forward on virtual devices Thread-Index: AQHUF7Amdnv0lRkeoUCXZ2BXFt7UrKSIHHTA Date: Tue, 10 Jul 2018 08:20:31 +0000 Message-ID: <74F120C019F4A64C9B78E802F6AD4CC278FC9F12@IRSMSX106.ger.corp.intel.com> References: <1882345510.2557424.1530213493803.JavaMail.zimbra@redhat.com> <329369015.3963546.1530802400841.JavaMail.zimbra@redhat.com> <1706940680.3976131.1530805573796.JavaMail.zimbra@redhat.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNGViMzBhZGQtMzVjNS00ODY1LTg2MGQtYTE5MTVkMmI3YjVkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiNzNcL3FNeVRTSlU0Y3FlZGN4WFNuK1VpSUFodlNHQUJpckRFTk1LM1VcLzhWamJpQjBHbHBDSnRSRndPYU5ickxrIn0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [dpdk-users] Traffic doesn't forward on virtual devices X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2018 08:20:35 -0000 >=20 > Bala Sankaran writes: >=20 > > Perfect! > > > > Thanks for the help. > > > > ----- Original Message ----- > >> From: "Keith Wiles" > >> To: "Bala Sankaran" > >> Cc: users@dpdk.org, "Aaron Conole" > >> Sent: Thursday, July 5, 2018 11:41:46 AM > >> Subject: Re: [dpdk-users] Traffic doesn't forward on virtual devices > >> > >> > >> > >> > On Jul 5, 2018, at 9:53 AM, Bala Sankaran > wrote: > >> > > >> > Greetings, > >> > > >> > I am currently using dpdk version 17.11.2. I see that there are a fe= w > other > >> > revisions in 17.11.3, followed by the latest stable version of 18.02= .2. > >> > > >> > Based on the issues I have faced so far (see Original > >> > Message below), would you suggest that I go for > >> > another version? If yes, which one? In essence, my question is, woul= d > >> > resorting to a different version of dpdk solve my current issue of > >> > virtqueue id being invalid? > >> > > >> > 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 > >> latest 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 > >> include them in the CC line on your questions as sometimes they miss t= he > >> emails as the volume can be high at times. >=20 > Thanks Keith. >=20 > I took a quick look and it seems like the queues are not setting up > correctly between OvS and testpmd? Probably there's a step missing > somewhere, although nothing in either the netdev-dpdk.c from OvS nor the > rte_ethdev was obvious to stand out to me. >=20 > I've CC'd Maxime, Ian, and Ciara - maybe they have a better idea to try? Hi, I think the appropriate driver to use in this test on the test-pmd side mig= ht be virtio-user. Follow the same steps just change your vdev test-pmd arguments to: --vdev=3D'net_virtio_user0,path=3D/usr/local/var/run/openvswitch/vhu0' Thanks, Ciara >=20 > >> > > >> > Thanks > >> > > >> > ----- 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 > >> >> > >> >> > >> >> Hello team, > >> >> > >> >> I am working on a project to do PVP tests on dpdk. As a first step,= I > >> >> would > >> >> like to get traffic flow between tap devices. I'm in process of set= ting up > >> >> the architecture, in which I've used testpmd to forward traffic > between > >> >> two > >> >> virtual devices(tap and vhost users) over a bridge. > >> >> > >> >> While I'm at it, I've identified that the internal dev_attached fla= g never > >> >> 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 bein= g > >> >> referenced is out of range. > >> >> > >> >> 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? > >> >> > >> >> Here's how I configured my setup after installing dpdk and > openvswitch: > >> >> > >> >> 1. To start ovs-ctl: > >> >> /usr/local/share/openvswitch/scripts/ovs-ctl start > >> >> > >> >> 2. Setup hugepages: > >> >> echo '2048' > /proc/sys/vm/nr_hugepages > >> >> > >> >> 3. Add a new network namespace: > >> >> ip netns add ns1 > >> >> > >> >> 4. Add and set a bridge: > >> >> ovs-vsctl add-br dpdkbr0 -- set Bridge dpdkbr0 datapath_type=3Dnetd= ev > >> >> options:vhost-server-path=3D/usr/local/var/run/openvswitch/vhu0 > >> >> ovs-vsctl show > >> >> > >> >> 5. Add a vhost user to the bridge created: > >> >> ovs-vsctl add-port dpdkbr0 vhu0 -- set Interface vhu0 > >> >> type=3Ddpdkvhostuserclient > >> >> > >> >> 6. Execute bash on the network namespace: > >> >> ip netns exec ns1 bash > >> >> > >> >> 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 > >> >> > >> >> > >> >> 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. > >> >> > >> >> I would greatly appreciate any help from your end. > >> >> > >> >> Thanks. > >> >> > >> >> ------------------------------------------------- > >> >> Bala Sankaran > >> >> Networking Services Intern > >> >> Red Hat Inc ., > >> >> > >> > ------------------------------------------------- > >> > Bala Sankaran > >> > Networking Services Intern > >> > >> Regards, > >> Keith > >> > >> > > > > -------------------------------------------------- > > Bala Sankaran > > Networking Services Intern > > Red Hat Inc .,