On Wed, 2015-10-28 at 18:39 +0100, Paolo Abeni wrote:

This patch changes how the multipath hash is computed for locally
generated UDP or TCP flows: now the hash comprises also l4 information
(source and destination port).

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.

Signed-off-by: Paolo Abeni <pabeni@redhat.com>

Please note that many skb already have a l4 hash. No need to perform yet
another dissection.

This would work even for tunneled traffic...

See commit 4b1b865e4e97e336316f30e32af36d71e98bdabc for an example.