From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH] ethdev: expose link status and speed using xstats Date: Wed, 20 Jan 2016 10:36:04 -0800 Message-ID: <20160120103604.2e32c9ac@xeon-e3> References: <1453300086-3756-1-git-send-email-harry.van.haaren@intel.com> <3240763.FVKPEEMrPZ@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail-pf0-f179.google.com (mail-pf0-f179.google.com [209.85.192.179]) by dpdk.org (Postfix) with ESMTP id EB74C8DAF for ; Wed, 20 Jan 2016 19:35:56 +0100 (CET) Received: by mail-pf0-f179.google.com with SMTP id e65so8826987pfe.0 for ; Wed, 20 Jan 2016 10:35:56 -0800 (PST) In-Reply-To: <3240763.FVKPEEMrPZ@xps13> 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 Wed, 20 Jan 2016 16:13:34 +0100 Thomas Monjalon wrote: > > We already have the rte_eth_link_get function. Why not let users > > continue to use that? It's well defined, it is simple, and it is > > consistent. +1 API's should not duplicate results (DRY) That said, it would be useful to have some way to get statistics on the number of link transitions and time since last change. But this ideally should be in rte_eth_link_get() but that wouldn't be ABI compatiable.