From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Wang, Liang-min" Subject: Re: [PATCH 2/2] ethtool: add new library to provide ethtool-alike APIs Date: Sat, 30 May 2015 19:40:46 +0000 Message-ID: References: <1432946276-9424-1-git-send-email-liang-min.wang@intel.com> <1432946276-9424-3-git-send-email-liang-min.wang@intel.com> <20150530084800.56e3585e@urahara> <20150530122617.1bf2cd18@urahara> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" To: Stephen Hemminger Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 49ACF2716 for ; Sat, 30 May 2015 21:40:49 +0200 (CEST) In-Reply-To: <20150530122617.1bf2cd18@urahara> Content-Language: en-US List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Sat, 30 May 2015 16:16:01 +0000 "Wang, Liang-min" wrote: > >The design decision is to keep ethdev as THE interface for all the exter= nal API, so ethtool APIs are designed based upon ethdev API. At the meantim= e, the ethtool APIs are designed to enable users to migrate designs based u= pon kernel-space ethtool. The open/close/start are put in place to enable q= uick migration. > >But there is no open/close/start in ethtool in kernel. >Anyway ethtool is currently on the disfavored list from kernel developers. >What about netlink or something better? > >Remember each new API creates more long term compatiablity and ABI issues. >So I am against introducing any new API that does the same thing as existi= ng API's. Just to clarify APIs supported by this ethtool api: there are net_open and = net_stop and no net_start. Both functions are put in place to support net_d= evice_ops::ndo_open and net_device_ops::ndo_close as defined in linux/netde= vice.h