DPDK usage discussions
 help / color / mirror / Atom feed
From: Shivaram Mysore <shivaram.mysore@gmail.com>
To: abhishek jain <ashujain9727@gmail.com>
Cc: users@dpdk.org, Hristo.Trifonov@ul.ie, mxkvcs@rit.edu
Subject: Re: [dpdk-users] Tx/Rx not increasing on DPDK interface
Date: Tue, 12 Dec 2017 09:55:11 -0800	[thread overview]
Message-ID: <CAJRY+jp+rCD2q66fvjc8+O_oJz3NcqJEbqGBwt-89B=OoomyoQ@mail.gmail.com> (raw)
In-Reply-To: <CA+9-Lvv8J=SRWZ3zF+nt5D_b+9HRR3ZvHc3VKRLOt1-Tc8Oowg@mail.gmail.com>

With the info provided, I am not sure how your OVS is setup.  You may want
to consider looking at my presentation and code available @
https://github.com/shivarammysore/faucetsdn-intel/tree/master/src/ubuntu/zesty/ovs_281
to get DPDK working

On Tue, Dec 12, 2017 at 3:14 AM, abhishek jain <ashujain9727@gmail.com>
wrote:

> Hi Team
>
> I'm having one physical interface configured as DPDK interface using below
> command..
>
> dpdk_nic_bind --bind=igb_uio  0000:03:00.1
>
>
> and it succesffluy appears in DPDK configured interfaces..
>
>  dpdk_nic_bind --status
>
> Network devices using DPDK-compatible driver
> ============================================
> 0000:03:00.1 'Ethernet Connection X552/X557-AT 10GBASE-T' drv=igb_uio
> unused=vfio-pci,uio_pci_generic
>
>
> Once it is configured,I'm adding this interface in OVS-DPDK bridge using
> below command..
>
> ovs-vsctl add-port br-int eth3 tag=4 -- set Interface eth3
> type=dpdkvhostuser options:dpdk-devargs=0000:03:00.1
>
>
> After this configuration,when I'm sending traffic from physical
> interface,I'm not able to see any packets reaching OVS br-int .
>
>
>  tcpdump -i br-int
>
> Hoever once I unbind the physical interface  with ixgbe driver,I'm able to
> see the packets reaching OVS DPDK br-int.
>
>
> Please let me know regarding this.
>
> Regars
> Abhishek Jain
>

      reply	other threads:[~2017-12-12 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 11:14 abhishek jain
2017-12-12 17:55 ` Shivaram Mysore [this message]

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='CAJRY+jp+rCD2q66fvjc8+O_oJz3NcqJEbqGBwt-89B=OoomyoQ@mail.gmail.com' \
    --to=shivaram.mysore@gmail.com \
    --cc=Hristo.Trifonov@ul.ie \
    --cc=ashujain9727@gmail.com \
    --cc=mxkvcs@rit.edu \
    --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).