From: "Wang, Haiyue" <haiyue.wang@intel.com>
To: "Zhang, AlvinX" <alvinx.zhang@intel.com>, "Guo, Jia" <jia.guo@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] net/igc: fix Rx error counter for badlen packets
Date: Thu, 1 Apr 2021 06:16:26 +0000 [thread overview]
Message-ID: <BN8PR11MB3795B7EDDDE8943E8D21D716F77B9@BN8PR11MB3795.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210401052043.15800-1-alvinx.zhang@intel.com>
> -----Original Message-----
> From: Zhang, AlvinX <alvinx.zhang@intel.com>
> Sent: Thursday, April 1, 2021 13:21
> To: Wang, Haiyue <haiyue.wang@intel.com>; Guo, Jia <jia.guo@intel.com>
> Cc: dev@dpdk.org; Zhang, AlvinX <alvinx.zhang@intel.com>; stable@dpdk.org
> Subject: [PATCH v2] net/igc: fix Rx error counter for badlen packets
>
> When the size of a packet in Rx channel is less than the minimum
> or greater than the maximum, the packet will be simultaneously
> counted by RLEC(Receive Length Error Count) and
> RUC(Receive Under Size Count)/ROC(Receive Oversize Count) registers.
>
> This patch fixes the issue of counting a length error packet twice
> when counting the total number of received error packets.
>
> Fixes: e6defdfddc3b ("net/igc: enable statistics")
> Cc: stable@dpdk.org
>
> Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com>
> ---
>
> V2: Refine commit log
> ---
> drivers/net/igc/igc_ethdev.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
Acked-by: Haiyue Wang <haiyue.wang@intel.com>
> --
> 1.8.3.1
next prev parent reply other threads:[~2021-04-01 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 1:16 [dpdk-stable] [PATCH] " Alvin Zhang
2021-04-01 1:57 ` Wang, Haiyue
2021-04-01 5:07 ` [dpdk-stable] [PATCH v2] " Alvin Zhang
2021-04-01 5:20 ` Alvin Zhang
2021-04-01 6:16 ` Wang, Haiyue [this message]
2021-04-01 7:45 ` Zhang, Qi Z
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=BN8PR11MB3795B7EDDDE8943E8D21D716F77B9@BN8PR11MB3795.namprd11.prod.outlook.com \
--to=haiyue.wang@intel.com \
--cc=alvinx.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.com \
--cc=stable@dpdk.org \
/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).