Thread (7 messages) flat view 7 messages, 2 authors, 2021-11-18

Re: [PATCHv2 net-next] Bonding: add missed_max option

From: Hangbin Liu <hidden>
Date: 2021-11-17 09:58:53

On Wed, Nov 17, 2021 at 08:40:25AM +0000, Jay Vosburgh wrote:
Hangbin Liu [off-list ref] wrote:
quoted
Currently, we use hard code number to verify if we are in the
arp_interval timeslice. But some user may want to reduce/extend
the verify timeslice. With the similar team option 'missed_max'
the uers could change that number based on their own environment.

The name of arp_misssed_max is not used as we may use this option for
Bonding IPv6 NS/NA monitor in future.
	Why reserve "arp_missed_max" for IPv6 which doesn't use ARP?  If
the option is for the ARP monitor, then prefixing it with "arp_" would
be consistent with the other arp_* options.
I didn't explain it clearly. I want to say:

I'm not using arp_misssed_max as the new option name because I plan to add
bonding IPv6 NS/NA monitor in future. At that time the option "missed_max"
could be used for both IPv4/IPv6 monitor.

I will update the commit description in next version.

Thanks
Hangbin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help