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

- From: Scott Feldman \<hidden\>
- Date: 2015-08-29 20:55:54 
- List: netdev
- Page: https://ratatoskr.run/netdev/2015/08/10995628
- Thread: https://ratatoskr.run/linux-api/2015/08/10995628/t.md

```text
On Sat, Aug 29, 2015 at 1:46 PM, David Miller [ref] wrote:
> From: Peter Nørlund <redacted>
> Date: Sat, 29 Aug 2015 22:31:15 +0200
>
>> On Sat, 29 Aug 2015 13:14:29 -0700 (PDT)
>> David Miller [ref] wrote:
>>
>>> From: <redacted>
>>> Date: Fri, 28 Aug 2015 22:00:47 +0200
>>>
>>> > 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.

That makes mapping the hash to offload hardware easier also.
```