From: Hangbin Liu <liuhangbin@gmail.com>
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH RFC net-next 0/5] bonding: add IPv6 NS/NA monitor support
Date: Thu, 27 Jan 2022 15:13:24 +0800 [thread overview]
Message-ID: <YfJGFHiiSBJdbxL3@Laptop-X1> (raw)
In-Reply-To: <66d6c646-d71d-91d3-993c-fc542bf77e0f@nvidia.com>
On Wed, Jan 26, 2022 at 01:47:45PM +0200, Nikolay Aleksandrov wrote:
> Hi,
> I'd imagine such option to work alongside ARP, i.e. to be able to have both
> ARP and ND targets at the same time. On Rx you can choose which one to check
> based on the protocol, at Tx the same. Then you can reuse and extend most of the
> current arp procedures to handle IPv6 as well. And most of all remove these ifs
> all around the code:
> + if (bond_slave_is_up(slave)) {
> + if (bond_do_ns_validate(bond))
> + bond_ns_send_all(bond, slave);
> + else
> + bond_arp_send_all(bond, slave);
> + }
>
> and just have one procedure that handles both if there are any targets for that protocol.
> That will completely remove the need for bond_do_ns_validate() helper.
Thanks, I will have a try.
>
> Also define BOND_MAX_ND_TARGETS as BOND_MAX_ARP_TARGETS just for the namesake.
Ah, yes.
>
> Another cosmetic nit: adjust for reverse xmas tree ordering of local variables all over.
OK, I will.
Thanks
Hangbin
prev parent reply other threads:[~2022-01-27 7:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 7:35 [PATCH RFC net-next 0/5] bonding: add IPv6 NS/NA monitor support Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 1/5] ipv6: separate ndisc_ns_create() from ndisc_send_ns() Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 2/5] Bonding: split bond_handle_vlan from bond_arp_send Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 3/5] bonding: add ip6_addr for bond_opt_value Hangbin Liu
2022-01-26 11:35 ` Nikolay Aleksandrov
2022-01-27 7:02 ` Hangbin Liu
2022-01-27 8:56 ` Nikolay Aleksandrov
2022-01-27 12:09 ` Hangbin Liu
2022-01-27 12:14 ` Nikolay Aleksandrov
2022-01-28 8:04 ` Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 4/5] bonding: add new parameter ns_targets Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 5/5] bonding: add new option ns_ip6_target Hangbin Liu
2022-01-26 11:47 ` [PATCH RFC net-next 0/5] bonding: add IPv6 NS/NA monitor support Nikolay Aleksandrov
2022-01-27 7:13 ` 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=YfJGFHiiSBJdbxL3@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=vfalico@gmail.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