From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: [PATCH RFC net-next 0/7] net/ipv6: Add support for path selection using hash of 5-tuple Date: Tue, 13 Feb 2018 13:03:14 +0200 Message-ID: References: <20180213000602.12150-1-dsahern@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: Linux Netdev List , Roopa Prabhu , Nikolay Aleksandrov , Ido Schimmel , Tom Herbert To: David Ahern Return-path: Received: from mail-it0-f49.google.com ([209.85.214.49]:51389 "EHLO mail-it0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934079AbeBMLDP (ORCPT ); Tue, 13 Feb 2018 06:03:15 -0500 Received: by mail-it0-f49.google.com with SMTP id 193so7718373iti.1 for ; Tue, 13 Feb 2018 03:03:15 -0800 (PST) In-Reply-To: <20180213000602.12150-1-dsahern@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On Tue, Feb 13, 2018 at 2:05 AM, David Ahern 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.