From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com
 [209.85.192.172]) by dpdk.org (Postfix) with ESMTP id 9C4CBE62
 for <dev@dpdk.org>; Sat, 30 May 2015 21:26:15 +0200 (CEST)
Received: by pdfh10 with SMTP id h10so77350420pdf.3
 for <dev@dpdk.org>; Sat, 30 May 2015 12:26:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=Q1u8ZuIsY5Fg3wINO5hC6V2Yiv9vpk44V9X8w2YR5i4=;
 b=Tcur0F8ccMg6j7VwSrYJ4M6fSSF9tcrMWz+QN+g2C2++b6y/3Wj1plOOV8MZH00MHg
 4yXw6N/LzEFLXDTtPcENZPm+QTQFI5YQ0HnhQL7jP8B1MctM1cJ1jCfoJtOP+YIapYgb
 q6HvBlGdaLnvsVhWi77FfrXgXNQzEnIhGd9IiGOC/hvsd1z5FFcYXj9uxNpFQsS4H7OQ
 cxPLABDzhPJLMj9yrqGMWsUmyvoPUXjqeBt0rwR1un04XowtxnUrjdRxFhxUWHoLPE+/
 d/OD1CaQ2dWUu1adkzPo1o3/rkm8hPNiv4l/Ls5PU75LzY/f5ic9sR8cOuK1BllZIEnK
 OPvg==
X-Gm-Message-State: ALoCoQkPotGfFfafZBm5/NLf48eBk5mEOmBnd13BN+2dnW5mVc4lQ0RjpQQbn+/agi7CU2g7os50
X-Received: by 10.70.96.139 with SMTP id ds11mr15833522pdb.98.1433013974643;
 Sat, 30 May 2015 12:26:14 -0700 (PDT)
Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net.
 [50.53.82.155])
 by mx.google.com with ESMTPSA id ni1sm9470035pdb.32.2015.05.30.12.26.14
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Sat, 30 May 2015 12:26:14 -0700 (PDT)
Date: Sat, 30 May 2015 12:26:17 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Wang, Liang-min" <liang-min.wang@intel.com>
Message-ID: <20150530122617.1bf2cd18@urahara>
In-Reply-To: <B6CB929FEBC10D4FAC4BCA7EF2298E2571764BCF@FMSMSX110.amr.corp.intel.com>
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>
 <B6CB929FEBC10D4FAC4BCA7EF2298E2571764BCF@FMSMSX110.amr.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] ethtool: add new library to provide
 ethtool-alike APIs
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Sat, 30 May 2015 19:26:16 -0000

On Sat, 30 May 2015 16:16:01 +0000
"Wang, Liang-min" <liang-min.wang@intel.com> wrote:

> The design decision is to keep ethdev as THE interface for all the external API, so ethtool APIs are designed based upon ethdev API. At the meantime, the ethtool APIs are designed to enable users to migrate designs based upon kernel-space ethtool. The open/close/start are put in place to enable quick 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 existing API's.