DPDK usage discussions
 help / color / mirror / Atom feed
From: Bala Sankaran <bsankara@redhat.com>
To: Keith Wiles <keith.wiles@intel.com>
Cc: users@dpdk.org, Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-users] Traffic doesn't forward on virtual devices
Date: Thu, 5 Jul 2018 11:46:13 -0400 (EDT)	[thread overview]
Message-ID: <1706940680.3976131.1530805573796.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <FA078466-7060-44E9-908A-D696272FC83B@intel.com>

Perfect!

Thanks for the help.

----- Original Message -----
> From: "Keith Wiles" <keith.wiles@intel.com>
> To: "Bala Sankaran" <bsankara@redhat.com>
> Cc: users@dpdk.org, "Aaron Conole" <aconole@redhat.com>
> 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 <bsankara@redhat.com> 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" <bsankara@redhat.com>
> >> To: users@dpdk.org
> >> Cc: "Aaron Conole" <aconole@redhat.com>
> >> 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 .,

  reply	other threads:[~2018-07-05 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1291144238.2553240.1530211305119.JavaMail.zimbra@redhat.com>
2018-06-28 19:18 ` Bala Sankaran
2018-07-05 14:53   ` Bala Sankaran
2018-07-05 15:41     ` Wiles, Keith
2018-07-05 15:46       ` Bala Sankaran [this message]
2018-07-09 18:10         ` Aaron Conole
2018-07-10  8:20           ` Loftus, Ciara
2018-07-10 17:37             ` Bala Sankaran
2018-07-11  8:12               ` Loftus, Ciara
2018-07-11 14:28                 ` Bala Sankaran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1706940680.3976131.1530805573796.JavaMail.zimbra@redhat.com \
    --to=bsankara@redhat.com \
    --cc=aconole@redhat.com \
    --cc=keith.wiles@intel.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).