From: "Zhang, Helin" <helin.zhang@intel.com>
To: Jay Rolette <rolette@infiniteio.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] BUG - KNI broken in 4.2 kernel
Date: Thu, 27 Aug 2015 15:56:16 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A8E7810@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CADNuJVpeWPFjpdHnmxDin+8zvRFmiDmh8NXW_MA-aEcVzgsy6Q@mail.gmail.com>
From: Jay Rolette [mailto:rolette@infiniteio.com]
Sent: Thursday, August 27, 2015 8:49 AM
To: Zhang, Helin
Cc: Stephen Hemminger; dev@dpdk.org
Subject: Re: [dpdk-dev] BUG - KNI broken in 4.2 kernel
On Thu, Aug 27, 2015 at 10:23 AM, Zhang, Helin <helin.zhang@intel.com<mailto:helin.zhang@intel.com>> wrote:
> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@networkplumber.org<mailto:stephen@networkplumber.org>]
> Sent: Wednesday, August 26, 2015 5:15 PM
> To: dev@dpdk.org<mailto:dev@dpdk.org>; Zhang, Helin
> Subject: BUG - KNI broken in 4.2 kernel
>
> The network device ops handles changed again.
>
> Does KNI really need to keep yet another copy of the Intel driver code.
Yes, it is a bit ugly. But there is no better way till now, as some of users want to have the functionality of KNI ethtool though limited now.
I have an idea that is to disable KNI ethtool support by default, as most of users may not care about it. Then these users will not be bothered by these type of issues.
Do you know of anyone that uses KNI that doesn't care about it? Since KNI presents as a normal network interface, it really needs to support the normal Linux commands (ifconfig, ethtool, ...)
Based on my experience, only one or two users asked for ethtool support, then we have it. Before that time, we don’t have KNI ethtool support.
I did not mean who uses KNI does not care about it, I mean for those users who don’t use KNI, they shouldn’t be bothered by the KNI compilation issues. That’s why I was thinking if we can disable it by default, but not remove it.
Regards,
Helin
Jay
For those users who are using KNI ethtool support, they need to fix the issues on any new versions of kernel or similar.
Any good ideas or comments?
Helin
> There already are 4 versions:
> 1. Out-of tree base driver
> 2. In-kernel mainline Linux driver
> 3. DPDK driver
> 4. KNI DPDK driver
>
> No wonder they can't stay in sync.
next prev parent reply other threads:[~2015-08-27 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 0:15 Stephen Hemminger
2015-08-27 8:41 ` Thomas Monjalon
2015-08-27 9:58 ` De Lara Guarch, Pablo
2015-08-27 15:23 ` Zhang, Helin
2015-08-27 15:49 ` Jay Rolette
2015-08-27 15:56 ` Zhang, Helin [this message]
2015-08-27 17:45 ` Stephen Hemminger
2015-08-27 17:53 ` Zhang, Helin
2015-08-28 12:44 ` Bruce Richardson
2015-08-28 15:48 ` Stephen Hemminger
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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A8E7810@SHSMSX104.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=rolette@infiniteio.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).