DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Qiu, Michael" <michael.qiu@intel.com>
To: Michael Qiu <qiudayu@cn.ibm.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ixgbe: reset hardware stat when initialize
Date: Wed, 20 May 2015 09:35:11 +0000	[thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E602860467FA19@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1431072861-28565-1-git-send-email-qiudayu@cn.ibm.com>

Any comments about this patch?

Thanks,
Michael

On 5/8/2015 4:14 PM, Michael Qiu wrote:
> From: Michael Qiu <michael.qiu@intel.com>
>
> When initialize the hardware, the stat should be reset.
> Otherwise when detach then attach port, the stat will not
> be re-init to zero.
>
> Signed-off-by: Michael Qiu <michael.qiu@intel.com>
> ---
>  lib/librte_pmd_ixgbe/ixgbe_ethdev.c | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/lib/librte_pmd_ixgbe/ixgbe_ethdev.c b/lib/librte_pmd_ixgbe/ixgbe_ethdev.c
> index 1b3b4b5..dbcc12a 100644
> --- a/lib/librte_pmd_ixgbe/ixgbe_ethdev.c
> +++ b/lib/librte_pmd_ixgbe/ixgbe_ethdev.c
> @@ -840,6 +840,9 @@ eth_ixgbe_dev_init(struct rte_eth_dev *eth_dev)
>  		return -EIO;
>  	}
>  
> +	/* Reset the hw statistics */
> +	ixgbe_dev_stats_reset(eth_dev);
> +
>  	/* disable interrupt */
>  	ixgbe_disable_intr(hw);
>  
> @@ -1015,6 +1018,9 @@ eth_ixgbevf_dev_init(struct rte_eth_dev *eth_dev)
>  	/* Disable the interrupts for VF */
>  	ixgbevf_intr_disable(hw);
>  
> +	/* Reset the hw statistics */
> +	ixgbevf_dev_stats_reset(eth_dev);
> +
>  	hw->mac.num_rar_entries = 128; /* The MAX of the underlying PF */
>  	diag = hw->mac.ops.reset_hw(hw);
>  


       reply	other threads:[~2015-05-20  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1431072861-28565-1-git-send-email-qiudayu@cn.ibm.com>
2015-05-20  9:35 ` Qiu, Michael [this message]
2015-06-11  7:29 ` [dpdk-dev] [PATCH v2] " Michael Qiu
2015-06-22 12:47   ` Iremonger, Bernard
2015-07-02 11:54     ` Qiu, Michael
2015-07-10 15:52     ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=533710CFB86FA344BFBF2D6802E602860467FA19@SHSMSX101.ccr.corp.intel.com \
    --to=michael.qiu@intel.com \
    --cc=dev@dpdk.org \
    --cc=qiudayu@cn.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).