From: Eric Dumazet <eric.dumazet@gmail.com>
To: Nikolay Aleksandrov <nikolay@redhat.com>
Cc: netdev@vger.kernel.org, fubar@us.ibm.com, andy@greyhouse.net,
davem@davemloft.net
Subject: Re: [PATCH net-next] bonding: change xmit hash functions to use skb_flow_dissect
Date: Fri, 19 Apr 2013 17:57:15 -0700 [thread overview]
Message-ID: <1366419435.16391.70.camel@edumazet-glaptop> (raw)
In-Reply-To: <1366412545-10829-1-git-send-email-nikolay@redhat.com>
On Sat, 2013-04-20 at 01:02 +0200, Nikolay Aleksandrov wrote:
> As Eric suggested earlier, bonding hash functions can make good use of
> skb_flow_dissect. The old use cases should have the same results, but
> there should be good improvement for tunnel users mostly over IPv4.
> I've kept the IPv6 address hashing algorithm and thus if a tunnel is
> used over IPv6 then the addresses will be the same but there still can be
> improvement because the ports from skb_flow_dissect will be mixed in.
> This also fixes a problem with protocol == ETH_P_8021Q load balancing.
Are you sure ? we don't look at skb->vlan_tci
> In case of non-dissectable packet, the algorithms fall back to L2
> hashing.
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@redhat.com>
> ---
> drivers/net/bonding/bond_main.c | 114 ++++++++++++++++++----------------------
> 1 file changed, 50 insertions(+), 64 deletions(-)
>
> diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
> index 5e22126..722d8c1 100644
> --- a/drivers/net/bonding/bond_main.c
> +++ b/drivers/net/bonding/bond_main.c
> @@ -77,6 +77,7 @@
> #include <net/net_namespace.h>
> #include <net/netns/generic.h>
> #include <net/pkt_sched.h>
> +#include <net/flow_keys.h>
> #include "bonding.h"
> #include "bond_3ad.h"
> #include "bond_alb.h"
> @@ -3271,94 +3272,79 @@ static struct notifier_block bond_netdev_notifier = {
>
> +
> + layer4_xor = ntohs(flow.port16[0] ^ flow.port16[1]);
> +
> + if (skb->protocol == htons(ETH_P_IPV6))
> + return (layer4_xor ^ bond_ipv6_hash(skb)) % count;
> + else
> + return (layer4_xor ^ bond_ipv4_hash(&flow)) % count;
> }
>
Not sure its worth doing this test, as IPv6 addresses are mixed already.
So just
hash = (__force u32)flow.ports ^
(__force u32)keys.dst ^
(__force u32)keys.src;
hash ^= (hash >> 16);
hash ^= (hash >> 8);
return hash % count;
next prev parent reply other threads:[~2013-04-20 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 23:02 [PATCH net-next] bonding: change xmit hash functions to use skb_flow_dissect Nikolay Aleksandrov
2013-04-20 0:57 ` Eric Dumazet [this message]
2013-04-20 6:12 ` Nikolay Aleksandrov
2013-04-20 15:52 ` Eric Dumazet
2013-04-20 16:38 ` Eric Dumazet
2013-04-20 16:46 ` Nikolay Aleksandrov
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=1366419435.16391.70.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.com \
/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