DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: SaurabhGL <saggarwal848@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Effect of Run pktgen application with NIC under linux control and dpdk control
Date: Tue, 21 Feb 2017 14:20:10 +0000	[thread overview]
Message-ID: <C8EE63A0-E40D-4F0B-9258-59ED026DF62E@intel.com> (raw)
In-Reply-To: <CALHp0uDEU_sNo6u4Gsfax-Ybru4C1xa-k58iZ52XDXazT__hmw@mail.gmail.com>


> On Feb 21, 2017, at 7:54 AM, SaurabhGL <saggarwal848@gmail.com> wrote:
> 
> Hi Dpdk Team,
> 
> I am new to dpdk and am trying to run dpdk pktgen application by command
> mentioned below :
> ./pktgen -c 0x1f -n 3 --vdev=eth_pcap0,iface=enp2s0 -- -P -m "[1:3].0"
> 
> Before run the application i execute the script named "dpdk-devbind.py
> --status" It's showing status as mentioned below:

The virtual devices will not show up in dpdk-devbind.py and if the enp2s0 is not suppose to be in the list, but I have not run the eth_pcap device before.

> 
> Network devices using DPDK-compatible driver
> ============================================
> <none>
> 
> Network devices using kernel driver
> ===================================
> 0000:02:00.0 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
> if=enp2s0 drv=r8169 unused= *Active*
> 0000:04:01.0 '82546EB Gigabit Ethernet Controller (Copper)' if=enp4s1f0
> drv=e1000 unused=
> 0000:04:01.1 '82546EB Gigabit Ethernet Controller (Copper)' if=enp4s1f1
> drv=e1000 unused=
> 
> Other network devices
> =====================
> <none>
> 
> It is showing no interface are under the DPDK-compatible driver list, Is it
> means that we are not using the interface enp2s0 with dpdk?
> if not, Is it affecting  on performance of pktgen application ?
> 
> And Next I to bring the interfaces "enp2s0" from kernel driver list to the
> "DPDK-compatible driver" list as shown below
> 
> Network devices using DPDK-compatible driver
> ============================================
> 0000:02:00.0 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
> drv=igb_uio unused=r8169,uio_pci_generic
> 
> Network devices using kernel driver
> ===================================
> 0000:04:01.0 '82546EB Gigabit Ethernet Controller (Copper)' if=enp4s1f0
> drv=e1000 unused=igb_uio,uio_pci_generic
> 0000:04:01.1 '82546EB Gigabit Ethernet Controller (Copper)' if=enp4s1f1
> drv=e1000 unused=igb_uio,uio_pci_generic
> 
> Other network devices
> =====================
> <none>
> 
> but I am not able to got the it interface name and not in active mode also,
> How to use now pktgen application without interface name?

I think the eth_pcap the interface needs to be owned by the kernel not DPDK, but I could wrong here.

When you use PCAP the first way does it work?

> 
> Thanks in advance for quick solution
> -- 
> Thanks & Regards
> 
> Saurabh Aggarwal

Regards,
Keith

      reply	other threads:[~2017-02-21 14:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 13:54 SaurabhGL
2017-02-21 14:20 ` Wiles, Keith [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=C8EE63A0-E40D-4F0B-9258-59ED026DF62E@intel.com \
    --to=keith.wiles@intel.com \
    --cc=saggarwal848@gmail.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).