* [PATCH net-next v2] ipv4: use l4 hash for locally generated multipath flows
@ 2015-10-29 21:20 Paolo Abeni
2015-11-02 19:39 ` David Miller
0 siblings, 1 reply; 2+ messages in thread
From: Paolo Abeni @ 2015-10-29 21:20 UTC (permalink / raw)
To: netdev
Cc: David S. Miller, Alexey Kuznetsov, James Morris,
Hideaki YOSHIFUJI, Patrick McHardy, pch
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>
---
net/ipv4/fib_semantics.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/ipv4/fib_semantics.c b/net/ipv4/fib_semantics.c
index 42778d9..f30df0e 100644
--- a/net/ipv4/fib_semantics.c
+++ b/net/ipv4/fib_semantics.c
@@ -1564,7 +1564,8 @@ void fib_select_path(struct net *net, struct fib_result *res,
#ifdef CONFIG_IP_ROUTE_MULTIPATH
if (res->fi->fib_nhs > 1 && fl4->flowi4_oif == 0) {
if (mp_hash < 0)
- mp_hash = fib_multipath_hash(fl4->saddr, fl4->daddr);
+ mp_hash = get_hash_from_flowi4(fl4) >> 1;
+
fib_select_multipath(res, mp_hash);
}
else
--
1.8.3.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH net-next v2] ipv4: use l4 hash for locally generated multipath flows
2015-10-29 21:20 [PATCH net-next v2] ipv4: use l4 hash for locally generated multipath flows Paolo Abeni
@ 2015-11-02 19:39 ` David Miller
0 siblings, 0 replies; 2+ messages in thread
From: David Miller @ 2015-11-02 19:39 UTC (permalink / raw)
To: pabeni; +Cc: netdev, kuznet, jmorris, yoshfuji, kaber, pch
From: Paolo Abeni <pabeni@redhat.com>
Date: Thu, 29 Oct 2015 22:20:40 +0100
> 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>
Applied, thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-11-02 19:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-10-29 21:20 [PATCH net-next v2] ipv4: use l4 hash for locally generated multipath flows Paolo Abeni
2015-11-02 19:39 ` David Miller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).