From: Weiping Pan <panweiping3@gmail.com>
To: netdev@vger.kernel.org
Cc: fubar@us.ibm.com, andy@greyhouse.net,
linux-kernel@vger.kernel.org, Weiping Pan <panweiping3@gmail.com>
Subject: [PATCH net V2 0/2] bonding:add aging mechanism to rlb table
Date: Thu, 22 Mar 2012 16:37:49 +0800 [thread overview]
Message-ID: <cover.1332405098.git.panweiping3@gmail.com> (raw)
Jiri Bohac(jbohac@suse.cz) found that once an IP address is recorded in the
rlb hash table, it stays there indefinitely. If this IP address is migrated
to a different host in the network, bonding still sends out ARP packets
that poison other systems' ARP caches with invalid information.
There are some attempts to fix this problem,
http://marc.info/?l=linux-netdev&m=133036407906892&w=4
http://marc.info/?l=linux-netdev&m=133057427414043&w=4
But they did not fix the root cause of the problem, that rlb table does not
have a aging mechanism, the entry is deemed valid for ever unless it is
replaced.
In this patchset I want to add aging mechanism to rlb table.
Assume RLB_MONITOR_DELAY is 2 seconds and RLB_WORK_COUNTER_TIMES is 3,
and we can tune them.
Every 6 seconds bonding will make all entries invalid.
Every 2 seconds, bonding will send arp requests to its all
clients, then if it receives corresponding arp reply, bonding will deem that
this entry is valid.
And we give a entry 3 opportunities to survive in 6 seconds.
V2:
add cover letter
Weiping Pan (2):
bonding:delete rlb entry if bond's ip is deleted
bonding:delete rlb entry at regular intervals
drivers/net/bonding/bond_alb.c | 130 ++++++++++++++++++++++++++++++++++++---
drivers/net/bonding/bond_alb.h | 9 +++
drivers/net/bonding/bond_main.c | 11 +++-
3 files changed, 138 insertions(+), 12 deletions(-)
--
1.7.4
next reply other threads:[~2012-03-22 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 8:37 Weiping Pan [this message]
2012-03-22 8:37 ` [PATCH net V2 1/2] bonding:delete rlb entry if bond's ip is deleted Weiping Pan
2012-03-22 8:37 ` [PATCH net V2 2/2] bonding:delete rlb entry at regular intervals Weiping Pan
2012-03-23 6:08 ` 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=cover.1332405098.git.panweiping3@gmail.com \
--to=panweiping3@gmail.com \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.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.