From: Jakub Kicinski <kuba@kernel.org>
To: Martyna Szapar-Mudlaw <martyna.szapar-mudlaw@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v3 0/2] Add link_down_events counters to ixgbe and ice drivers
Date: Mon, 12 May 2025 17:21:46 -0700 [thread overview]
Message-ID: <20250512172146.2f06e09f@kernel.org> (raw)
In-Reply-To: <20250512090515.1244601-2-martyna.szapar-mudlaw@linux.intel.com>
On Mon, 12 May 2025 11:05:14 +0200 Martyna Szapar-Mudlaw wrote:
> This series introduces link_down_events counters to the ixgbe and ice drivers.
> The counters are incremented each time the link transitions from up to down,
> allowing better diagnosis of link stability issues such as port flapping or
> unexpected link drops.
To confirm, will the counter increment:
- when link is held up by BMC / NC-SI or some other agent
and user does down/up on the host?
- when user reconfigures channels, attaches XDP etc?
Would be good to document that in the cover letter.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Martyna Szapar-Mudlaw <martyna.szapar-mudlaw@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [PATCH iwl-next v3 0/2] Add link_down_events counters to ixgbe and ice drivers
Date: Mon, 12 May 2025 17:21:46 -0700 [thread overview]
Message-ID: <20250512172146.2f06e09f@kernel.org> (raw)
In-Reply-To: <20250512090515.1244601-2-martyna.szapar-mudlaw@linux.intel.com>
On Mon, 12 May 2025 11:05:14 +0200 Martyna Szapar-Mudlaw wrote:
> This series introduces link_down_events counters to the ixgbe and ice drivers.
> The counters are incremented each time the link transitions from up to down,
> allowing better diagnosis of link stability issues such as port flapping or
> unexpected link drops.
To confirm, will the counter increment:
- when link is held up by BMC / NC-SI or some other agent
and user does down/up on the host?
- when user reconfigures channels, attaches XDP etc?
Would be good to document that in the cover letter.
next prev parent reply other threads:[~2025-05-13 0:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 9:05 [Intel-wired-lan] [PATCH iwl-next v3 0/2] Add link_down_events counters to ixgbe and ice drivers Martyna Szapar-Mudlaw
2025-05-12 9:05 ` Martyna Szapar-Mudlaw
2025-05-12 9:05 ` [Intel-wired-lan] [PATCH iwl-next v3 1/2] ice: add link_down_events statistic Martyna Szapar-Mudlaw
2025-05-12 9:05 ` Martyna Szapar-Mudlaw
2025-05-12 9:05 ` [Intel-wired-lan] [PATCH iwl-next v3 2/2] ixgbe: " Martyna Szapar-Mudlaw
2025-05-12 9:05 ` Martyna Szapar-Mudlaw
2025-05-13 0:21 ` Jakub Kicinski [this message]
2025-05-13 0:21 ` [PATCH iwl-next v3 0/2] Add link_down_events counters to ixgbe and ice drivers Jakub Kicinski
2025-05-14 13:44 ` [Intel-wired-lan] " Szapar-Mudlaw, Martyna
2025-05-14 13:44 ` Szapar-Mudlaw, Martyna
2025-05-14 14:42 ` [Intel-wired-lan] " Jakub Kicinski
2025-05-14 14:42 ` Jakub Kicinski
2025-05-14 14:59 ` [Intel-wired-lan] " Szapar-Mudlaw, Martyna
2025-05-14 14:59 ` Szapar-Mudlaw, Martyna
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=20250512172146.2f06e09f@kernel.org \
--to=kuba@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=martyna.szapar-mudlaw@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.