DPDK usage discussions
 help / color / mirror / Atom feed
From: Jay Rolette <rolette@infinite.io>
To: Andriy Berestovskyy <aber@semihalf.com>
Cc: sml <sml.caerus@gmail.com>, users <users@dpdk.org>
Subject: Re: [dpdk-users] Configuring MAC Address of KNI - Don't want random
Date: Tue, 12 Apr 2016 10:40:08 -0500	[thread overview]
Message-ID: <CADNuJVocBKGuyTN6pPX6s68V_7BJQThwJQZmxmazwkTpuvn0sA@mail.gmail.com> (raw)
In-Reply-To: <CAOysbxr4EgteH_kvHLYn9uhnLVWdYw2zq-fj2_J4OA_tW8p=JQ@mail.gmail.com>

On Mon, Apr 11, 2016 at 4:01 AM, Andriy Berestovskyy <aber@semihalf.com>
wrote:

> Hi sml,
> The KNI uses old ixgbe and igb Linux drivers in order to support
> ethtool. Here is the list of supported e1000 devices:
>
> http://dpdk.org/browse/dpdk/tree/lib/librte_eal/linuxapp/kni/ethtool/igb/e1000_hw.h#n37
>
> The list is somewhat shorter than the list of supported devices in
> DPDK itself. So there are some devices which work well in DPDK, but
> KNI generates random MACs for them.
>
> The DPDK community decided to get rid of the KNI, so your only option
> is to set the MAC on vEth using ip(8) or ifconfig(8). You can also add
> an option into the /etc/network/interfaces (or similar), so the MAC
> will be configured once your vEth device is up.
>

Sorry, but this is incorrect. DPDK has definitely NOT decided to get rid of
KNI.

There is a desire to find better solutions than KNI, but for that to
happen, there has to be something that provides equivalent functionality.
There are multiple products built on DPDK that rely on KNI for various
capabilities.

There are some proposals for ways to get away from KNI, but nothing
accepted or scheduled to replace or even deprecate KNI.

Jay

      parent reply	other threads:[~2016-04-12 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-09  5:41 sml
2016-04-11  9:01 ` Andriy Berestovskyy
2016-04-11 16:50   ` Jason Kwon
2016-04-12 11:46     ` Andriy Berestovskyy
2016-04-12 15:40   ` Jay Rolette [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=CADNuJVocBKGuyTN6pPX6s68V_7BJQThwJQZmxmazwkTpuvn0sA@mail.gmail.com \
    --to=rolette@infinite.io \
    --cc=aber@semihalf.com \
    --cc=sml.caerus@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).