DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Shankari Vaidyalingam <shankari.v2k6@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Interface name after bound to IGB
Date: Wed, 25 Mar 2015 15:17:25 +0000	[thread overview]
Message-ID: <20150325151724.GC5620@bricha3-MOBL3> (raw)
In-Reply-To: <CAGeyXNeubNBeCr25Tx6hjsJFJD7P188cOK4pdumYhF7Y0rbE7g@mail.gmail.com>

On Wed, Mar 25, 2015 at 08:44:51PM +0530, Shankari Vaidyalingam wrote:
> Hi Bruce,
> 
> 
> If I want to capture the packets received by the interface bound to IGB
> (DPDK interface) then I'd like to know what would be the interface name
> that must be given.
> 
> Regards
> Shankari.V
> 

To capture using DPDK, the port will be picked up automatically by DPDK init
sequence, or you can explicitly whitelist it via BDF, if you really want. To
capture using something that uses the kernel driver, e.g. using libpcap, you
need to unbind from igb_uio and bind back to the kernel driver again.

Regards,
/Bruce

> 
> On Wed, Mar 25, 2015 at 8:33 PM, Bruce Richardson <
> bruce.richardson@intel.com> wrote:
> 
> > On Wed, Mar 25, 2015 at 08:00:02PM +0530, Shankari Vaidyalingam wrote:
> > > Hi
> > >
> > > By what name is the NIC port identified after it is bound to the igb_uio
> > > driver (i.e after it becomes a DPDK interface)
> > > I'm asking this question because the interface does not get displayed in
> > > the output of the "ifconfig" after it gets bound to igb_uio driver.
> > >
> > >
> > > Regards
> > > Shankari.V
> >
> > Identified where, or to what? It still maintains the same PCI
> > bus-device-function
> > which can be used to identify it, if that is what you mean.
> >
> > /Bruce
> >

  reply	other threads:[~2015-03-25 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 14:30 Shankari Vaidyalingam
2015-03-25 15:03 ` Bruce Richardson
2015-03-25 15:14   ` Shankari Vaidyalingam
2015-03-25 15:17     ` Bruce Richardson [this message]
2015-03-25 15:20     ` Olivier MATZ
2015-03-26  3:58       ` Shankari Vaidyalingam
2015-03-26 11:07         ` Olivier MATZ

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=20150325151724.GC5620@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=shankari.v2k6@gmail.com \
    /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).