From: Jay Vosburgh <fubar@us.ibm.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bonding-devel@lists.sourceforge.net
Subject: Re: when using arp monitoring with bonding, why use broadcast arps?
Date: Tue, 04 Dec 2007 10:20:56 -0800 [thread overview]
Message-ID: <17022.1196792456@death> (raw)
In-Reply-To: <47558DFC.5050601@nortel.com>
Chris Friesen <cfriesen@nortel.com> wrote:
[...]
>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?
It ought to be a pretty straightforward change to have the
bond_arp_send() function perform a neigh_lookup() prior to calling
arp_create(), and use the result of the lookup (if any) in the
arp_create() call.
So, no, with the caveat that I haven't tried it, I don't see a
reason that bonding couldn't do what you're looking for.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
prev parent reply other threads:[~2007-12-04 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 17:27 when using arp monitoring with bonding, why use broadcast arps? Chris Friesen
2007-12-04 18:20 ` Jay Vosburgh [this message]
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=17022.1196792456@death \
--to=fubar@us.ibm.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=cfriesen@nortel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.