[PATCH v3 net 4/4] docs: net: bonding: remove mentions of trans_start
From: Vladimir Oltean <vladimir.oltean@nxp.com>
Date: 2022-07-31 12:41:44
Subsystem:
bonding driver, documentation, networking [general], the rest · Maintainers:
Jay Vosburgh, Jonathan Corbet, "David S. Miller", Eric Dumazet, Jakub Kicinski, Paolo Abeni, Linus Torvalds
ARP monitoring no longer depends on dev->last_rx or dev_trans_start(), so delete this information. Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com> --- Documentation/networking/bonding.rst | 9 --------- 1 file changed, 9 deletions(-)
diff --git a/Documentation/networking/bonding.rst b/Documentation/networking/bonding.rst
index 43be3782e5df..4ebbf21590c4 100644
--- a/Documentation/networking/bonding.rst
+++ b/Documentation/networking/bonding.rst@@ -1971,15 +1971,6 @@ uses the response as an indication that the link is operating. This gives some assurance that traffic is actually flowing to and from one or more peers on the local network. -The ARP monitor relies on the device driver itself to verify -that traffic is flowing. In particular, the driver must keep up to -date the last receive time, dev->last_rx. Drivers that use NETIF_F_LLTX -flag must also update netdev_queue->trans_start. If they do not, then the -ARP monitor will immediately fail any slaves using that driver, and -those slaves will stay down. If networking monitoring (tcpdump, etc) -shows the ARP requests and replies on the network, then it may be that -your device driver is not updating last_rx and trans_start. - 7.2 Configuring Multiple ARP Targets ------------------------------------
--
2.34.1