From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: bonding: Do we need netlink events for LACP status?
Date: Mon, 04 Mar 2024 22:33:27 -0800 [thread overview]
Message-ID: <32499.1709620407@famine> (raw)
In-Reply-To: <ZeaSkudOInw5rjbj@Laptop-X1>
Hangbin Liu <liuhangbin@gmail.com> wrote:
>A customer asked to add netlink event notifications for LACP bond state
>changes. With this, the network monitor could get the LACP state of bonding
>and port interfaces, and end user may change the down link port based
>on the current LACP state. Do you think if this is a reasonable case
>and do able? If yes, I will add it to my to do list.
I think I'm going to need some more detail here.
To make sure I understand, the suggestion here is to add netlink
notifications for transitions in the LACP mux state machine (ATTACHED,
COLLECTING, DISTRIBUTING, et al), correct? If not, then what
specifically do you mean?
Also, what does "change the down link port" mean?
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2024-03-05 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 3:33 bonding: Do we need netlink events for LACP status? Hangbin Liu
2024-03-05 6:33 ` Jay Vosburgh [this message]
2024-03-06 3:19 ` Hangbin Liu
2024-03-10 3:11 ` Jay Vosburgh
2024-03-11 11:44 ` Hangbin Liu
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=32499.1709620407@famine \
--to=jay.vosburgh@canonical.com \
--cc=liuhangbin@gmail.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 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).