From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 744FE591A for ; Thu, 27 Aug 2015 17:24:01 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP; 27 Aug 2015 08:24:00 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,422,1437462000"; d="scan'208";a="549636804" Received: from pgsmsx102.gar.corp.intel.com ([10.221.44.80]) by FMSMGA003.fm.intel.com with ESMTP; 27 Aug 2015 08:23:59 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by PGSMSX102.gar.corp.intel.com (10.221.44.80) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 27 Aug 2015 23:23:58 +0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.210]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.143]) with mapi id 14.03.0224.002; Thu, 27 Aug 2015 23:23:57 +0800 From: "Zhang, Helin" To: Stephen Hemminger Thread-Topic: BUG - KNI broken in 4.2 kernel Thread-Index: AQHQ4F1tD2pEerUhVU+SKdrxnL4ao54f9u4A Date: Thu, 27 Aug 2015 15:23:56 +0000 Message-ID: References: <20150826171516.7160bcb2@urahara> In-Reply-To: <20150826171516.7160bcb2@urahara> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2015 15:24:02 -0000 > -----Original Message----- > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > Sent: Wednesday, August 26, 2015 5:15 PM > To: dev@dpdk.org; Zhang, Helin > Subject: BUG - KNI broken in 4.2 kernel >=20 > The network device ops handles changed again. >=20 > 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 user= s 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 o= f users may not care about it. Then these users will not be bothered by the= se type of issues. For those users who are using KNI ethtool support, they need to fix the iss= ues 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 >=20 > No wonder they can't stay in sync.