From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] enic: state change from link-down to link-up not recognized Date: Wed, 30 Mar 2016 19:35:01 +0200 Message-ID: <1540849.gS1UoX4J3q@xps13> References: <1458953117-13817-1-git-send-email-johndale@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: John Daley Return-path: Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by dpdk.org (Postfix) with ESMTP id 57571952 for ; Wed, 30 Mar 2016 19:36:54 +0200 (CEST) Received: by mail-wm0-f45.google.com with SMTP id 127so106153259wmu.1 for ; Wed, 30 Mar 2016 10:36:54 -0700 (PDT) In-Reply-To: <1458953117-13817-1-git-send-email-johndale@cisco.com> 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" 2016-03-25 17:45, John Daley: > When the enic was disabled, link notification was correctly disabled > in the NIC but the software indicator that it was disabled was not > updated (vdev->notify_pa not set to 0). When the link came back up, > enic did not re-enable notification in the NIC. > > This affected bonding when a enic slave device link bounced. > > The fix is to unconditionally enable notification when the enic is > enabled. > > Fixes: 9913fbb91df0 ("enic/base: common code") > > Signed-off-by: John Daley > Reviewed-by: Nelson Escobar Applied, thanks