DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Kevin Wilson <wkevils@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] ethtool and igb/ixgbe (kni)
Date: Tue, 28 Oct 2014 10:01:53 +0000	[thread overview]
Message-ID: <20141028100153.GA12148@BRICHA3-MOBL> (raw)
In-Reply-To: <CAGXs5wWMMzGkJF6V1E5w1eeO2FZ_zgfWvoeRWt+G75ScU0Z=qA@mail.gmail.com>

On Mon, Oct 27, 2014 at 07:49:03PM +0200, Kevin Wilson wrote:
> Poke!
> Can anybody advice about this question ?
> Kevin
> 
> On Fri, Oct 24, 2014 at 12:54 PM, Kevin Wilson <wkevils@gmail.com> wrote:
> > Hi,
> >
> > I am looking in the file hierarchy of dpdk, and I see that under
> > /dpdk-1.7.1/lib/librte_eal/linuxapp/kni/ethtool
> > we have:
> > igb  ixgbe  README
> >
> > My question is: why the igb and ixgbe are on this path, under ethtool
> > ? are they related
> > to ethtool in any way ?
> >
> >
> > The README does not explain it.
> >
> > Regards,
> > Kevin

The code for igb and ixgbe are under that path to allow the kernel net devs 
created by the KNI to have ethtool support for manipulating the underlying 
NIC.

/Bruce

      reply	other threads:[~2014-10-28  9:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 10:54 Kevin Wilson
2014-10-27 17:49 ` Kevin Wilson
2014-10-28 10:01   ` Bruce Richardson [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=20141028100153.GA12148@BRICHA3-MOBL \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=wkevils@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).