DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, HailinX" <hailinx.xu@intel.com>
To: "Deng, KaiwenX" <kaiwenx.deng@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Deng, KaiwenX" <kaiwenx.deng@intel.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>,
	Tiwei Bie <tiwei.bie@intel.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: RE: [PATCH] net/intel: fix ixgbe get macsec stats
Date: Tue, 20 May 2025 07:24:30 +0000	[thread overview]
Message-ID: <MW4PR11MB5912C619E34C0870B878A2339F9FA@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250520011316.561890-1-kaiwenx.deng@intel.com>

> -----Original Message-----
> From: Kaiwen Deng <kaiwenx.deng@intel.com>
> Sent: Tuesday, May 20, 2025 9:13 AM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Deng, KaiwenX <kaiwenx.deng@intel.com>; Burakov,
> Anatoly <anatoly.burakov@intel.com>; Medvedkin, Vladimir
> <vladimir.medvedkin@intel.com>; Tiwei Bie <tiwei.bie@intel.com>; Wenzhuo
> Lu <wenzhuo.lu@intel.com>
> Subject: [PATCH] net/intel: fix ixgbe get macsec stats
> 
> The ixgbe macsec registers are not cleared on read. Reading the registers and
> then accumulating the values will cause macsec stats errors. Each time the
> data is queried via the testpmd command “show port stats xstats all”, the
> macsec statistics are increased.
> 
> This commit will add macsec offset stats to record initial data and update
> macsec stats based on offset stats.
> 
> Fixes: b35d309710fe ("net/ixgbe: add MACsec offload")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Kaiwen Deng <kaiwenx.deng@intel.com>
> ---
Tested-by: Xu, HailinX <hailinx.xu@intel.com>

      reply	other threads:[~2025-05-20  7:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20  1:13 Kaiwen Deng
2025-05-20  7:24 ` Xu, HailinX [this message]

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=MW4PR11MB5912C619E34C0870B878A2339F9FA@MW4PR11MB5912.namprd11.prod.outlook.com \
    --to=hailinx.xu@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=kaiwenx.deng@intel.com \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=vladimir.medvedkin@intel.com \
    --cc=wenzhuo.lu@intel.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).