[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMhtpmcNRNH9p5a2=RHCPZq1HW_y6pnPF45UAFVeCDgang@mail.gmail.com>
Date: Tue, 13 Feb 2018 13:03:14 +0200
From: Or Gerlitz <gerlitz.or@...il.com>
To: David Ahern <dsahern@...il.com>
Cc: Linux Netdev List <netdev@...r.kernel.org>,
Roopa Prabhu <roopa@...ulusnetworks.com>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
Ido Schimmel <idosch@...lanox.com>,
Tom Herbert <tom@...bertland.com>
Subject: Re: [PATCH RFC net-next 0/7] net/ipv6: Add support for path selection
using hash of 5-tuple
On Tue, Feb 13, 2018 at 2:05 AM, David Ahern <dsahern@...il.com> wrote:
> Hardware supports multipath selection using the standard L4 5-tuple
> instead of just L3 and the flow label. In addition, some network
> operators prefer IPv6 path selection to use the 5-tuple.
The HW supports using flow label and AFAIK that is the preferred approach
by the community (?)
> To that end, add support to IPv6 for multipath hash policy
so a question comes up if/what are the disadvantaged
to support 5-tuple. E.g Tom was commenting that such DPI is problematic
when multiple IPv6 header extensions are used.
> similar to bf4e0a3db97eb ("net: ipv4: add support for ECMP hash policy choice").
> The default is still L3 which covers source and destination addresses
> along with flow label and IPv6 protocol.
>
> A separate sysctl is added for IPv6, allowing IPv4 and IPv6 to use
> different algorithms if desired.
Powered by blists - more mailing lists