Thread (2 messages) 2 messages, 2 authors, 2015-08-29

Re: [PATCH v2 net-next 0/3] ipv4: Hash-based multipath routing

From: David Miller <hidden>
Date: 2015-08-29 20:46:28
Also in: netdev

Possibly related (same subject, not in this thread)

From: Peter Nørlund <pch-chEQUL3jiZBWk0Htik3J/w@public.gmane.org>
Date: Sat, 29 Aug 2015 22:31:15 +0200
On Sat, 29 Aug 2015 13:14:29 -0700 (PDT)
David Miller [off-list ref] wrote:
quoted
From: pch-chEQUL3jiZBWk0Htik3J/w@public.gmane.org
Date: Fri, 28 Aug 2015 22:00:47 +0200
quoted
When the routing cache was removed in 3.6, the IPv4 multipath
algorithm changed from more or less being destination-based into
being quasi-random per-packet scheduling. This increases the risk
of out-of-order packets and makes it impossible to use multipath
together with anycast services.
Don't even try to be fancy.

Simply kill the round-robin stuff off completely, and make hash based
routing the one and only mode, no special configuration stuff
necessary.
I like the sound of that! Just to be clear - are you telling me to
stick with L3 and skip the L4 part?
For now it seems best to just do L3 and make ipv4 and ipv6 behave the
same.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help