Re: [net-next v3] ipv6: sr: Compute flowlabel for outer IPv6 header of seg6 encap mode

2018-04-26 Thread Ahmed Abdelsalam
On Wed, 25 Apr 2018 13:03:04 -0400 (EDT) David Miller wrote: > From: Ahmed Abdelsalam > Date: Tue, 24 Apr 2018 20:23:16 +0200 > > > ECMP (equal-cost multipath) hashes are typically computed on the packets' > > 5-tuple(src IP, dst IP, src port, dst

Re: [net-next v3] ipv6: sr: Compute flowlabel for outer IPv6 header of seg6 encap mode

2018-04-25 Thread David Miller
From: Ahmed Abdelsalam Date: Tue, 24 Apr 2018 20:23:16 +0200 > ECMP (equal-cost multipath) hashes are typically computed on the packets' > 5-tuple(src IP, dst IP, src port, dst port, L4 proto). > > For encapsulated packets, the L4 data is not readily available and ECMP >

Re: [net-next v3] ipv6: sr: Compute flowlabel for outer IPv6 header of seg6 encap mode

2018-04-25 Thread David Lebrun
On 04/24/2018 07:23 PM, Ahmed Abdelsalam wrote: Signed-off-by: Ahmed Abdelsalam Acked-by: David Lebrun

[net-next v3] ipv6: sr: Compute flowlabel for outer IPv6 header of seg6 encap mode

2018-04-24 Thread Ahmed Abdelsalam
ECMP (equal-cost multipath) hashes are typically computed on the packets' 5-tuple(src IP, dst IP, src port, dst port, L4 proto). For encapsulated packets, the L4 data is not readily available and ECMP hashing will often revert to (src IP, dst IP). This will lead to traffic polarization on a