From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 8D6B01BDD6 for ; Thu, 5 Jul 2018 17:46:16 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id F12A730001EE; Thu, 5 Jul 2018 15:46:15 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id DC54D171DC; Thu, 5 Jul 2018 15:46:15 +0000 (UTC) Received: from zmail18.collab.prod.int.phx2.redhat.com (zmail18.collab.prod.int.phx2.redhat.com [10.5.83.21]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id C3A524BB78; Thu, 5 Jul 2018 15:46:13 +0000 (UTC) Date: Thu, 5 Jul 2018 11:46:13 -0400 (EDT) From: Bala Sankaran To: Keith Wiles Cc: users@dpdk.org, Aaron Conole Message-ID: <1706940680.3976131.1530805573796.JavaMail.zimbra@redhat.com> In-Reply-To: References: <1882345510.2557424.1530213493803.JavaMail.zimbra@redhat.com> <329369015.3963546.1530802400841.JavaMail.zimbra@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.18.25.124, 10.4.195.11] Thread-Topic: [dpdk-users] Traffic doesn't forward on virtual devices Thread-Index: oQTMFRAawVHbwy4YZZ9aWPlHFRqacrwmn7/y4mqY1QDrMqcQuQ== X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.41]); Thu, 05 Jul 2018 15:46:16 +0000 (UTC) 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:46:17 -0000 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 few 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, would > > 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 the > emails as the volume can be high at times. > > > > > 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 setting 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 flag 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 being > >> 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=netdev > >> options:vhost-server-path=/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=dpdkvhostuserclient > >> > >> 6. Execute bash on the network namespace: > >> ip netns exec ns1 bash > >> > >> 7. Use testpmd and connect the namespaces: > >> testpmd --socket-mem=512 > >> --vdev='eth_vhost0,iface=/usr/local/var/run/openvswitch/vhu0,queues=1' > >> --vdev='net_tap0,iface=tap0' --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 .,