ipv4: use l4 hash for locally generated multipath flows
authorPaolo Abeni <pabeni@redhat.com>
Thu, 29 Oct 2015 21:20:40 +0000 (22:20 +0100)
committerDavid S. Miller <davem@davemloft.net>
Mon, 2 Nov 2015 19:38:43 +0000 (14:38 -0500)
commit9920e48b830a0f4ec06bcbf0ec3147c88ae72bac
treeffc26343183c1249bc2456622bf733e6ca66bbcf
parent1032a6687168af9509615879d513f77e4049062e
ipv4: use l4 hash for locally generated multipath flows

This patch changes how the multipath hash is computed for locally
generated flows: now the hash comprises l4 information.

This allows better utilization of the available paths when the existing
flows have the same source IP and the same destination IP: with l3 hash,
even when multiple connections are in place simultaneously, a single path
will be used, while with l4 hash we can use all the available paths.

v2 changes:
- use get_hash_from_flowi4() instead of implementing just another l4 hash
  function

Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/fib_semantics.c