From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [RFC 09/14] sfc: use new rte_eth_link helpers Date: Mon, 17 Jul 2017 09:02:29 -0700 Message-ID: <20170717090229.48abee36@xeon-e3> References: <20170714183027.16021-1-stephen@networkplumber.org> <20170714183027.16021-10-stephen@networkplumber.org> <60caca67-cfb9-c474-7fa9-faa7752fdaf1@solarflare.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: To: Andrew Rybchenko Return-path: Received: from mail-pf0-f172.google.com (mail-pf0-f172.google.com [209.85.192.172]) by dpdk.org (Postfix) with ESMTP id D598D47CD for ; Mon, 17 Jul 2017 18:02:32 +0200 (CEST) Received: by mail-pf0-f172.google.com with SMTP id q86so78529014pfl.3 for ; Mon, 17 Jul 2017 09:02:32 -0700 (PDT) In-Reply-To: <60caca67-cfb9-c474-7fa9-faa7752fdaf1@solarflare.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 Sun, 16 Jul 2017 16:48:50 +0300 Andrew Rybchenko wrote: > On 07/14/2017 09:30 PM, Stephen Hemminger wrote: > > Use the new API (_rte_eth_link_update) to handle link status update. > > ALso fixes a bug where this driver was not returning -1 when link status changed. > > It is really good that you raise it, since: > - as far as I can see the return value of the link_update is never used > - return value is not described and it is unclear what is meant by "link > status changed" since initial point is unspecified > > We have interpreted link status change as change in data->dev_link > made in the current execution flow, but not in parallel execution flow. All drivers must do the same thing. Private interpretation is not good.