From: Hangbin Liu <liuhangbin@gmail.com>
To: Jay Vosburgh <jay.vosburgh@canonical.com>
Cc: netdev@vger.kernel.org
Subject: Re: bonding: Do we need netlink events for LACP status?
Date: Mon, 11 Mar 2024 19:44:39 +0800 [thread overview]
Message-ID: <Ze7up2WpWa3Yv5Ap@Laptop-X1> (raw)
In-Reply-To: <15143.1710040289@famine>
On Sat, Mar 09, 2024 at 07:11:29PM -0800, Jay Vosburgh wrote:
> Generally speaking, I don't see an issue with adding these type
> of netlink events, as in normal usage the volume will be low.
>
> Looking at the code, I think it would be a matter of adding the
> new IFLA_BOND_LACP_STUFF labels, updating bond_fill_slave_info() and
> maybe bond_fill_info() to populate the netlink message for those new
> IFLAs. Add a call to call_netdevice_notifiers() in ad_mux_machine()
> when the state changes, using a new event type that would need to be
> handled by rtnetlink_event().
Thank Jay, I will add this on my todo list.
Hangbin
prev parent reply other threads:[~2024-03-11 11:44 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
2024-03-06 3:19 ` Hangbin Liu
2024-03-10 3:11 ` Jay Vosburgh
2024-03-11 11:44 ` Hangbin Liu [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=Ze7up2WpWa3Yv5Ap@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=jay.vosburgh@canonical.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.