From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: BUG - KNI broken in 4.2 kernel Date: Thu, 27 Aug 2015 10:45:43 -0700 Message-ID: <20150827104543.0138ab53@urahara> References: <20150826171516.7160bcb2@urahara> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" To: "Zhang, Helin" Return-path: Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com [209.85.220.53]) by dpdk.org (Postfix) with ESMTP id E7E75591A for ; Thu, 27 Aug 2015 19:45:32 +0200 (CEST) Received: by pacgr6 with SMTP id gr6so14915574pac.3 for ; Thu, 27 Aug 2015 10:45:32 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, 27 Aug 2015 15:56:16 +0000 "Zhang, Helin" wrote: > Based on my experience, only one or two users asked for ethtool support, = then we have it. Before that time, we don=E2=80=99t have KNI ethtool suppor= t. > I did not mean who uses KNI does not care about it, I mean for those user= s who don=E2=80=99t use KNI, they shouldn=E2=80=99t be bothered by the KNI = compilation issues. That=E2=80=99s why I was thinking if we can disable it = by default, but not remove it. > =C2=A0 > Regards, > Helin Can KNI instead use DPDK hooks to provide generic ethtool semantics. That way it would work with all hardware.