From: Nikolay Aleksandrov <razor@blackwall.org>
To: Tonghao Zhang <tonghao@bamaicloud.com>, netdev@vger.kernel.org
Cc: Jay Vosburgh <jv@jvosburgh.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Zengbing Tu <tuzengbing@didiglobal.com>
Subject: Re: [PATCH net-next v4 4/4] net: bonding: add tracepoint for 802.3ad
Date: Wed, 14 May 2025 12:39:36 +0300 [thread overview]
Message-ID: <cd45f194-0978-4e58-8c97-15494061f754@blackwall.org> (raw)
In-Reply-To: <DDF908383E15A2CE+20250514092534.27472-5-tonghao@bamaicloud.com>
On 5/14/25 12:25, Tonghao Zhang wrote:
> Users can monitor NIC link status changes through netlink. However, LACP
> protocol failures may occur despite operational physical links. There is
> no way to detect LACP state changes. This patch adds tracepoint at LACP state
> transition.
>
> Cc: Jay Vosburgh <jv@jvosburgh.net>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Paolo Abeni <pabeni@redhat.com>
> Cc: Simon Horman <horms@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Andrew Lunn <andrew+netdev@lunn.ch>
> Signed-off-by: Tonghao Zhang <tonghao@bamaicloud.com>
> Signed-off-by: Zengbing Tu <tuzengbing@didiglobal.com>
> ---
> drivers/net/bonding/bond_3ad.c | 6 ++++++
> include/trace/events/bonding.h | 37 ++++++++++++++++++++++++++++++++++
> 2 files changed, 43 insertions(+)
> create mode 100644 include/trace/events/bonding.h
>
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2025-05-14 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250514092534.27472-1-tonghao@bamaicloud.com>
2025-05-14 9:25 ` [PATCH net-next v4 1/4] net: bonding: add broadcast_neighbor option for 802.3ad Tonghao Zhang
2025-05-14 9:36 ` Nikolay Aleksandrov
2025-05-14 9:46 ` Nikolay Aleksandrov
2025-05-14 9:25 ` [PATCH net-next v4 2/4] net: bonding: add broadcast_neighbor netlink option Tonghao Zhang
2025-05-14 9:25 ` [PATCH net-next v4 3/4] net: bonding: send peer notify when failure recovery Tonghao Zhang
2025-05-14 9:39 ` Nikolay Aleksandrov
2025-05-14 9:25 ` [PATCH net-next v4 4/4] net: bonding: add tracepoint for 802.3ad Tonghao Zhang
2025-05-14 9:39 ` Nikolay Aleksandrov [this message]
2025-05-15 9:30 ` Jay Vosburgh
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=cd45f194-0978-4e58-8c97-15494061f754@blackwall.org \
--to=razor@blackwall.org \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonghao@bamaicloud.com \
--cc=tuzengbing@didiglobal.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