From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v2] kni: use kni_ethtool_ops only with unknown drivers Date: Fri, 30 Nov 2018 15:38:15 -0800 Message-ID: <20181130153815.3be2f30b@xeon-e3> References: <20181130192946.13732-1-iryzhov@nfware.com> <20181130194750.13870-1-iryzhov@nfware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Igor Ryzhov Return-path: Received: from mail-pg1-f193.google.com (mail-pg1-f193.google.com [209.85.215.193]) by dpdk.org (Postfix) with ESMTP id B59111B5CA for ; Sat, 1 Dec 2018 00:38:18 +0100 (CET) Received: by mail-pg1-f193.google.com with SMTP id n2so3152995pgm.3 for ; Fri, 30 Nov 2018 15:38:18 -0800 (PST) In-Reply-To: <20181130194750.13870-1-iryzhov@nfware.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, 30 Nov 2018 22:47:50 +0300 Igor Ryzhov 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 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) Then again why does KNI exist at all? What is missing from virtio user which is faster anyway.