summaryrefslogtreecommitdiff
path: root/Documentation/networking/bonding.rst
diff options
context:
space:
mode:
authorVladimir Oltean <vladimir.oltean@nxp.com>2022-07-31 15:41:08 +0300
committerJakub Kicinski <kuba@kernel.org>2022-08-04 05:20:13 +0300
commitcba8d8f57dfb1d01d961a0e50e7fddb82df57ad7 (patch)
tree68ce7f01a394516f08b9d36579bbc3f1fb81bf64 /Documentation/networking/bonding.rst
parent08b403d5bf07d9e0d97ba12649b198eee42f826d (diff)
downloadlinux-cba8d8f57dfb1d01d961a0e50e7fddb82df57ad7.tar.xz
docs: net: bonding: remove mentions of trans_start
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> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'Documentation/networking/bonding.rst')
-rw-r--r--Documentation/networking/bonding.rst9
1 files changed, 0 insertions, 9 deletions
diff --git a/Documentation/networking/bonding.rst b/Documentation/networking/bonding.rst
index 53a18ff7cf23..7823a069a903 100644
--- a/Documentation/networking/bonding.rst
+++ b/Documentation/networking/bonding.rst
@@ -1982,15 +1982,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
------------------------------------