RE: [PATCH net-next v1 0/2] bonding: Extend arp_ip_target format to allow for a list of vlan tags.

Hi David,

quoted

The current implementation of the arp monitor builds a list of vlan-tags by
following the chain of net_devices above the bond. See: bond_verify_device_path().
Unfortunately with some configurations this is not possible. One example is
when an ovs switch is configured above the bond.

This change extends the "arp_ip_target" parameter format to allow for a list of
vlan tags to be included for each arp target. This new list of tags is optional
and may be omitted to preserve the current format and process of gathering tags.
When provided the list of tags circumvents the process of gathering tags by
using the supplied list. An empty list can be provided to simply skip the the
process of gathering tags.

The purposed new format for arp_ip_target is:
arp_ip_target=ipv4-address[vlan-tag\...],...

Examples:
arp_ip_target=10.0.0.1,10.0.0.2 (Determine tags automatically for both targets)
arp_ip_target=10.0.0.1[]        (Don't add any tags, don't gather tags)
arp_ip_target=10.0.0.1[100/200] (Don't gather tags, use supplied list of tags)
arp_ip_target=10.0.0.1,10.0.0.2[100] (add vlan 100 tag for 10.0.0.2.
                                      Gather tags for 10.0.0.1.)

Thanks for the update. What about the IPv6 NS targets? Will you support it
or only the arp targets?

Thank you for the input.

My initial plan is to support IPv4, but I will ensure that it won't adversely impact IPv6.

BTW, when add or update the parameter, please also update the bond documents
and iproute2 cmd.

Will do.

Thanks
Hangbin

David Wilder (wilder@us.ibm.com)