From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] net/ixgbevf: fix stats update after a PF reset Date: Tue, 28 Mar 2017 17:22:52 +0200 Message-ID: <1981763.1ss0qQn5ig@xps13> References: <1484154254-31387-1-git-send-email-olivier.matz@6wind.com> <20170314104640.32b06adb@platinum> <20170324151148.5c3d9f9d@platinum> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Olivier Matz , "Dai, Wei" , Guo Fengtian , ferruh.yigit@intel.com To: "Zhang, Helin" , "Ananyev, Konstantin" Return-path: Received: from mail-wr0-f180.google.com (mail-wr0-f180.google.com [209.85.128.180]) by dpdk.org (Postfix) with ESMTP id E51CBCFA0 for ; Tue, 28 Mar 2017 17:22:53 +0200 (CEST) Received: by mail-wr0-f180.google.com with SMTP id l43so108779496wre.1 for ; Tue, 28 Mar 2017 08:22:53 -0700 (PDT) In-Reply-To: <20170324151148.5c3d9f9d@platinum> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Please ixgbe maintainers, what can be done for this fix? 2017-03-24 15:11, Olivier Matz: > Hi, > > (remove stable@dpdk.org) > > On Tue, 14 Mar 2017 10:46:40 +0100, Olivier Matz wrote: > > Hi Wei, > > > > On Thu, 16 Feb 2017 17:49:22 +0100, Olivier Matz wrote: > > > Hi Wei, > > > > > > On Thu, 9 Feb 2017 14:50:05 +0000, "Dai, Wei" wrote: > > > > > -----Original Message----- > > > > > From: Dai, Wei > > > > > Sent: Thursday, February 9, 2017 10:38 PM > > > > > To: 'Olivier Matz' ; dev@dpdk.org; Zhang, > > > > > Helin ; Ananyev, Konstantin > > > > > > > > > > Cc: Guo Fengtian ; stable@dpdk.org > > > > > Subject: RE: [dpdk-dev] [PATCH] net/ixgbevf: fix stats update after > > > > > a PF reset > > > > > > > > > > The stats register can rewind to zero when the port is running for > > > > > a long period. So I am afraid that this check is not always correct. > > > > > Why not introduce a variable to directly indicate whether the > > > > > resulted stats should be updated or not. > > > > > > > > Another way is to clear > > > > hw_stats->last_vfgprc/last_vfgorc/last_vfgptc/last_vfmprc at the same > > > > time PF is set down. > > > > > > > > > > Can we know easily in VF if the PF was set down? > > > > Any guideline for this? Or is it something we cannot fix? > > > > Is any maintainer available to help to fix that? > > Unfortunately I don't have enough knowledge on this driver to do the fix > by myself. It would be helpful to have some guidelines by a maintainer so > I can understand what is the proper way to fix the issue. > > Thanks, > Olivier