From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [PATCH v2] kni: use kni_ethtool_ops only with
 unknown drivers
Date: Tue, 18 Dec 2018 18:13:45 +0000
Message-ID: <7eab0eec-335a-be47-2406-9c989d13e981@intel.com>
References: <20181130192946.13732-1-iryzhov@nfware.com>
 <20181130194750.13870-1-iryzhov@nfware.com> <20181130153815.3be2f30b@xeon-e3>
 <7f929055-b55a-e839-9927-96787db88094@intel.com>
 <CAF+s_FymAB014duGBhgbyOSKvrO3RLvpWL5uAtvdUca3Miy5og@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Cc: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
To: Igor Ryzhov <iryzhov@nfware.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga17.intel.com (mga17.intel.com [192.55.52.151])
 by dpdk.org (Postfix) with ESMTP id 2F47B1B57C
 for <dev@dpdk.org>; Tue, 18 Dec 2018 19:13:48 +0100 (CET)
In-Reply-To: <CAF+s_FymAB014duGBhgbyOSKvrO3RLvpWL5uAtvdUca3Miy5og@mail.gmail.com>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 12/3/2018 2:06 PM, Igor Ryzhov wrote:
> Hi Ferruh,
> 
> What about the patch?
> 
> I also support dropping ethtool for ixgbe and i40e, but to save generic ethtool_ops
> with .get_link implementation, because it's an essential function that works
> correctly
> after proper implementation of carrier status that was merged into 18.11.
> 
> Also, other ethtool operations may be implemented in a driver-independent way using
> the same concept as for netdev_ops.

"carrier status" relies on the sample app support also relies on kni net_device
sysfs interface.
It is good target to have ethtool support in a driver-independent way, please
share more details and lets discuss them.

> 
> On Mon, Dec 3, 2018 at 4:09 PM Ferruh Yigit <ferruh.yigit@intel.com
> <mailto:ferruh.yigit@intel.com>> wrote:
> 
>     On 11/30/2018 11:38 PM, Stephen Hemminger wrote:
>     > On Fri, 30 Nov 2018 22:47:50 +0300
>     > Igor Ryzhov <iryzhov@nfware.com <mailto:iryzhov@nfware.com>> wrote:
>     >
>     >> Current implementation of kni_ethtool_ops just uses corresponding
>     >> ethtool_ops function of underlying driver for all functions except for
>     >> .get_link. This commit sets kni->net_dev->ethtool_ops directly to the
>     >> ethtool_ops of the corresponding driver.
>     >>
>     >> For unknown drivers (all but ixgbe and i40e) we still use
>     >> kni_ethtool_ops with implemented .get_link function.
>     >>
>     >> Signed-off-by: Igor Ryzhov <iryzhov@nfware.com <mailto:iryzhov@nfware.com>>
>     >
>     > Why does KNI still support ethtool which:
>     >   1. Only works on a subset of devices
>     >   2. Requires a 3rd implmentation of the HW device (Linux, DPDK, and KNI)
> 
>     +1 to drop ethtool support, last time we tried concern was anybody may be using
>     it, perhaps we can try again.
> 
>     >
>     > Then again why does KNI exist at all? What is missing from virtio user which
>     > is faster anyway.
>     >
>