From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH iwl-next] ice: do not reset MDD counters on VF reset
Date: Wed, 1 Apr 2026 16:14:33 -0700 [thread overview]
Message-ID: <09421682-7837-4f5a-a0ca-0baf9879eea6@intel.com> (raw)
In-Reply-To: <20260327072236.129802-2-aleksandr.loktionov@intel.com>
On 3/27/2026 12:22 AM, Aleksandr Loktionov wrote:
> From: Mark Rustad <mark.d.rustad@intel.com>
>
> Do not clear MDD event counters on VF reset, to be consistent with
> how VF statistics are not reset either. This allows accumulation of
> MDD events across resets so that persistent misbehavior can be
> tracked and reported more accurately.
>
> Fixes: 12bb018c538c ("ice: Refactor VF reset")
> Signed-off-by: Mark Rustad <mark.d.rustad@intel.com>
> Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
> ---
>
> drivers/net/ethernet/intel/ice/ice_vf_lib.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_vf_lib.c b/drivers/net/ethernet/intel/ice/ice_vf_lib.c
> index 7d33f09..9bcc739 100644
> --- a/drivers/net/ethernet/intel/ice/ice_vf_lib.c
> +++ b/drivers/net/ethernet/intel/ice/ice_vf_lib.c
> @@ -227,8 +227,6 @@ static void ice_vf_clear_counters(struct ice_vf *vf)
>
> vf->num_mac = 0;
> vf->num_mac_lldp = 0;
> - memset(&vf->mdd_tx_events, 0, sizeof(vf->mdd_tx_events));
> - memset(&vf->mdd_rx_events, 0, sizeof(vf->mdd_rx_events));
> }
>
> /**
AI Review says:
There's a documentation issue in
drivers/net/ethernet/intel/ice/ice_main.c that should be addressed. The
comment in ice_mdd_maybe_reset_vf() states:
> /* VF MDD event counters will be cleared by reset, so print the event
> * prior to reset.
> */
This comment contradicts the new behavior introduced by this patch.
Since the memset calls are removed, MDD event counters now persist
across VF resets rather than being cleared. The comment should be
updated to reflect that counters are accumulated across resets to track
persistent misbehavior, which is the intent documented in the commit
message.
Also, the threading on your sends seems to be off. If you are going to
send them together, please make them part of a series. If you are
treating them individually, please send them that way.
The target trees also seem off; some 'net' and some 'iwl-next' patches
with Fixes: that sound to be bug fixes. I'm working through and sorting
what's been sent, but please try to tag things properly on future sends.
Thanks,
Tony
next prev parent reply other threads:[~2026-04-01 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 7:22 [PATCH iwl-next] ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() Aleksandr Loktionov
2026-03-27 7:22 ` [PATCH iwl-next] ice: do not reset MDD counters on VF reset Aleksandr Loktionov
2026-04-01 23:14 ` Tony Nguyen [this message]
2026-03-27 7:22 ` [PATCH iwl-next] ice: check cross-timestamp timeout bits Aleksandr Loktionov
2026-04-02 0:01 ` [Intel-wired-lan] " Jacob Keller
2026-04-03 9:03 ` Simon Horman
2026-03-27 7:22 ` [PATCH iwl-next] ice: fix AQ error code comparison in ice_set_pauseparam() Aleksandr Loktionov
2026-04-03 12:10 ` Simon Horman
2026-03-27 7:22 ` [PATCH iwl-next] ice: call netif_keep_dst() once when entering switchdev mode Aleksandr Loktionov
2026-04-03 12:41 ` Simon Horman
2026-04-03 11:57 ` [PATCH iwl-next] ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() Simon Horman
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=09421682-7837-4f5a-a0ca-0baf9879eea6@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.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