From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <stephen@networkplumber.org> 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 <dev@dpdk.org>; Thu, 27 Aug 2015 19:45:32 +0200 (CEST) Received: by pacgr6 with SMTP id gr6so14915574pac.3 for <dev@dpdk.org>; Thu, 27 Aug 2015 10:45:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=/mjPiiizUbIT7gULwJuOwEYEmQUJobzbEND0u1bXCRc=; b=MbJYHtC9FkZNoVCWqXvcxi2OGxHK1HlG3gdi+LUcKg19MRdmriFCb67FAYO22omtCh x+eG5hZyBZCL6ty7Cg2j9SlKRigmth7fw3sv7uhKpV4hYiI92KjYpkRnsT/y6A+ULedT pxXxcj4uyvvi0/mlfUG81V1KCtCJuFh5gtialXFM6ntOV+3iTXJ70SWjpbV8xuhRJY7V ek20HKgrq/6ERlK0y24AZ5gCzmqdzjGfe+DW9WY1Vp2OVDo3lSiJt8/LfNlU6we3VudS 38Xxk5UL8w3wZfTdzGYKiliLfm1FipQg/z4NrSJq3loqbjSdoSjjSZZwE+NvArMIsPqT TAUw== X-Gm-Message-State: ALoCoQmvVJA2K5Q0qCilSP2z9+6JtBn7USyvdXhJATeNd8cRjB9WFHzyEnNOd0j2UpWoxrC0GOhE X-Received: by 10.68.217.102 with SMTP id ox6mr8429324pbc.158.1440697532201; Thu, 27 Aug 2015 10:45:32 -0700 (PDT) Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by smtp.gmail.com with ESMTPSA id rg10sm3092454pbc.33.2015.08.27.10.45.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Aug 2015 10:45:31 -0700 (PDT) Date: Thu, 27 Aug 2015 10:45:43 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: "Zhang, Helin" <helin.zhang@intel.com> Message-ID: <20150827104543.0138ab53@urahara> In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A8E7810@SHSMSX104.ccr.corp.intel.com> References: <20150826171516.7160bcb2@urahara> <F35DEAC7BCE34641BA9FAC6BCA4A12E70A8E774E@SHSMSX104.ccr.corp.intel.com> <CADNuJVpeWPFjpdHnmxDin+8zvRFmiDmh8NXW_MA-aEcVzgsy6Q@mail.gmail.com> <F35DEAC7BCE34641BA9FAC6BCA4A12E70A8E7810@SHSMSX104.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" <dev@dpdk.org> Subject: Re: [dpdk-dev] BUG - KNI broken in 4.2 kernel X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 27 Aug 2015 17:45:33 -0000 On Thu, 27 Aug 2015 15:56:16 +0000 "Zhang, Helin" <helin.zhang@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=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.