From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yk0-f177.google.com (mail-yk0-f177.google.com [209.85.160.177]) by dpdk.org (Postfix) with ESMTP id 5C521591A for ; Thu, 27 Aug 2015 17:49:25 +0200 (CEST) Received: by ykbi184 with SMTP id i184so24216431ykb.2 for ; Thu, 27 Aug 2015 08:49:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jjQFYrbCqu/YuBkZHPU9W7oTGnzM67iW7tLoViQogwQ=; b=NrAYlSfnljwiE5DWlOjPFIMeIoN8U2hHRWo9WmCCuWWiaah1PNuF4CzmbD7XhwzlMd 1e5TgHaCA4PJubhq8e1HW6+ptf6v6ix5X7JsuSb0II4s5e+yE2i4Zg7tFfvCCLf+E3d7 7Yt7OARoKovCF01PI1QBwVNJ8E2zCDoN9sFn/4Ulllb0ZEVaIUNWhh6+kNhrGPtDPqef xTgY1eOUlwItrAXhF6X5O2hqJdvIThDvoL1dg94wPMHhDHk6u9SctbGjlfFf17oVE3er EaT+2kzjBsgheqCshkOBgVNphzFxqXr3bNvq8rvskb7wwBtHk3Mor06iDvGJDtKFf8vo bmQQ== X-Gm-Message-State: ALoCoQnFVLjEIRMkqf+wPClCGHBY0TcLfh4OOKI7TUBlYGONO1UKheIEJaU3mSMr0i4bnl13d4OR MIME-Version: 1.0 X-Received: by 10.170.216.70 with SMTP id i67mr3930350ykf.15.1440690564784; Thu, 27 Aug 2015 08:49:24 -0700 (PDT) Received: by 10.37.25.212 with HTTP; Thu, 27 Aug 2015 08:49:24 -0700 (PDT) In-Reply-To: References: <20150826171516.7160bcb2@urahara> Date: Thu, 27 Aug 2015 10:49:24 -0500 Message-ID: From: Jay Rolette To: "Zhang, Helin" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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:49:25 -0000 On Thu, Aug 27, 2015 at 10:23 AM, Zhang, Helin wrote: > > > > -----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 > > > > 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, ...) 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. >