RE: [PATCH v4 net-next 0/2] ipv4: Hash-based multipath routing

2015-09-29 Thread David Laight
From: Peter Nørlund > Sent: 29 September 2015 12:29 ... > As for using L4 hashing with anycast, CloudFlare apparently does L4 > hashing - they could have disabled it, but they didn't. Besides, > analysis of my own load balancers showed that only one in every > 500,000,000 packets is fragmented.

Re: [PATCH v4 net-next 0/2] ipv4: Hash-based multipath routing

2015-09-29 Thread Peter Nørlund
On Mon, 28 Sep 2015 19:55:41 -0700 (PDT) David Miller wrote: > From: David Miller > Date: Mon, 28 Sep 2015 19:33:55 -0700 (PDT) > > > From: Peter Nørlund > > Date: Wed, 23 Sep 2015 21:49:35 +0200 > > > >> When the routing cache was

Re: [PATCH v4 net-next 0/2] ipv4: Hash-based multipath routing

2015-09-28 Thread David Miller
From: Peter Nørlund Date: Wed, 23 Sep 2015 21:49:35 +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

Re: [PATCH v4 net-next 0/2] ipv4: Hash-based multipath routing

2015-09-28 Thread David Miller
From: David Miller Date: Mon, 28 Sep 2015 19:33:55 -0700 (PDT) > From: Peter Nørlund > Date: Wed, 23 Sep 2015 21:49:35 +0200 > >> When the routing cache was removed in 3.6, the IPv4 multipath algorithm >> changed >> from more or less being