From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: KNI Questions
Date: Thu, 15 Dec 2016 09:16:08 -0800 [thread overview]
Message-ID: <20161215091608.25ab1b43@xeon-e3> (raw)
In-Reply-To: <53ad7e36-380c-e5b7-a002-1690d2e63603@intel.com>
On Thu, 15 Dec 2016 11:53:59 +0000
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> Hi Stephen,
>
> <...>
>
> >
> > Which raises a couple of questions:
> > 1. Why is DPDK still keeping KNI support for Intel specific ethtool functionality.
> > This always breaks, is code bloat, and means a 3rd copy of base code (Linux, DPDK PMD, + KNI)
>
> I agree on you comments related to the ethtool functionality,
> but right now that is a functionality that people may be using, I think
> we should not remove it without providing an alternative to it.
>
> >
> > 2. Why is KNI not upstream?
> > If not acceptable due to security or supportablity then why does it still exist?
>
> I believe you are one of the most knowledgeable person in the mail list
> on upstreaming, any support is welcome.
It should be upstreamable but I doubt it would make it past the maintainer.
Mostly because it supports DPDK which he is not in favor of but also since
it is a specialized interface only usable by DPDK, ie. not a general infrastructure.
next prev parent reply other threads:[~2016-12-15 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 23:40 KNI broken again with 4.9 kernel Stephen Hemminger
2016-12-15 10:25 ` Ferruh Yigit
2016-12-15 11:53 ` KNI Questions Ferruh Yigit
2016-12-15 17:16 ` Stephen Hemminger [this message]
2016-12-15 17:26 ` John Fastabend
2016-12-15 12:01 ` KNI broken again with 4.9 kernel Mcnamara, John
2016-12-15 12:55 ` Jay Rolette
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=20161215091608.25ab1b43@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.