Skip to content

Commit 0307d58

Browse files
vincentbernatdavem330
authored andcommitted
bonding: add documentation for peer_notif_delay
Ability to tweak the interval between peer notifications has been added in 07a4dde ("bonding: add an option to specify a delay between peer notifications") but the documentation was not updated. Signed-off-by: Vincent Bernat <vincent@bernat.ch> Signed-off-by: David S. Miller <davem@davemloft.net>
1 parent fe4e8db commit 0307d58

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

Documentation/networking/bonding.txt

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -706,9 +706,9 @@ num_unsol_na
706706
unsolicited IPv6 Neighbor Advertisements) to be issued after a
707707
failover event. As soon as the link is up on the new slave
708708
(possibly immediately) a peer notification is sent on the
709-
bonding device and each VLAN sub-device. This is repeated at
710-
each link monitor interval (arp_interval or miimon, whichever
711-
is active) if the number is greater than 1.
709+
bonding device and each VLAN sub-device. This is repeated at
710+
the rate specified by peer_notif_delay if the number is
711+
greater than 1.
712712

713713
The valid range is 0 - 255; the default value is 1. These options
714714
affect only the active-backup mode. These options were added for
@@ -727,6 +727,16 @@ packets_per_slave
727727
The valid range is 0 - 65535; the default value is 1. This option
728728
has effect only in balance-rr mode.
729729

730+
peer_notif_delay
731+
732+
Specify the delay, in milliseconds, between each peer
733+
notification (gratuitous ARP and unsolicited IPv6 Neighbor
734+
Advertisement) when they are issued after a failover event.
735+
This delay should be a multiple of the link monitor interval
736+
(arp_interval or miimon, whichever is active). The default
737+
value is 0 which means to match the value of the link monitor
738+
interval.
739+
730740
primary
731741

732742
A string (eth0, eth2, etc) specifying which slave is the

0 commit comments

Comments
 (0)