[dpdk-dev] BUG - KNI broken in 4.2 kernel

Zhang, Helin helin.zhang at intel.com
Thu Aug 27 19:53:50 CEST 2015

> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen at networkplumber.org]
> Sent: Thursday, August 27, 2015 10:46 AM
> To: Zhang, Helin
> Cc: Jay Rolette; dev at dpdk.org
> Subject: Re: [dpdk-dev] BUG - KNI broken in 4.2 kernel
> On Thu, 27 Aug 2015 15:56:16 +0000
> "Zhang, Helin" <helin.zhang at intel.com> wrote:
> > 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
> Can KNI instead use DPDK hooks to provide generic ethtool semantics.
> That way it would work with all hardware.
I am not sure if I understood your idea correctly.
My personal point is that the best KNI ethtool support should be processed in user space application.
Sure if we want to support standard Linux ethtool commands, the KNI kernel driver should have a mechanism to work together with user space application. Is that what you said of hooks?
But this may need huge efforts on it.
Sure ideas on ethtool support improvements are always welcome!


More information about the dev mailing list