From: "Chris Friesen" <cfriesen@nortel.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bonding-devel@lists.sourceforge.net
Subject: when using arp monitoring with bonding, why use broadcast arps?
Date: Tue, 04 Dec 2007 11:27:24 -0600 [thread overview]
Message-ID: <47558DFC.5050601@nortel.com> (raw)
We have a network with a number of nodes using bonding with arp
monitoring. The arp interval is set to 100ms.
Unfortunately, the bonding code sends the arp packets to the hardware
broadcast address, which means that the number of these arp packets seen
by each node goes up with the number of nodes on the network.
One of the nodes has a fairly low-powered cpu and handles most things in
microengine code, but arp packets get handled in software. All these
broadcast arps slow this node down noticeably.
Is there any particular reason why the bonding code couldn't use unicast
arp packets if the "arp_ip_target" has a valid entry in the sender's arp
table?
Thanks,
Chris
next reply other threads:[~2007-12-04 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 17:27 Chris Friesen [this message]
2007-12-04 18:20 ` when using arp monitoring with bonding, why use broadcast arps? Jay Vosburgh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47558DFC.5050601@nortel.com \
--to=cfriesen@nortel.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).