From: John <linux@8192.net>
To: netdev@vger.kernel.org
Cc: andy@greyhouse.net
Subject: [PATCH 0/2] bonding: Doesn't support IPv6
Date: Fri, 28 Oct 2011 18:08:00 -0700 [thread overview]
Message-ID: <4EAB51F0.6030105@8192.net> (raw)
Currently the "bonding" driver does not support load balancing outgoing
traffic in LACP mode for IPv6 traffic. IPv4 (and TCP or UDP over IPv4)
are currently supported; this patch adds transmit hashing for IPv6 (and
TCP or UDP over IPv6), bringing IPv6 up to par with IPv4 support in the
bonding driver.
The algorithm chosen (xor'ing the bottom three quads and then xor'ing
that down into the bottom byte) was chosen after testing almost 400,000
unique IPv6 addresses harvested from server logs. This algorithm had the
most even distribution for both big- and little-endian architectures
while still using few instructions.
Fragmented IPv6 packets are handled the same way as fragmented IPv4
packets, ie, they are not balanced based on layer 4 information.
Additionally, IPv6 packets with intermediate headers are not balanced
based on layer 4 information. In practice these intermediate headers are
rare and this should not cause any problems, the alternative (a
packet-parsing loop and look-up table) seemed slow and complicated for
little gain.
This is an update to a prior patch I submitted. This version includes
bounds checking not present in the original driver or my prior patch.
Included with the patch is an update to the bonding documentation.
Patch has been tested and performs as expected.
John
reply other threads:[~2011-10-29 1:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EAB51F0.6030105@8192.net \
--to=linux@8192.net \
--cc=andy@greyhouse.net \
--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.