From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ahern Subject: Re: [PATCH RFC net-next 5/7] net/ipv6: Add support for path selection using hash of 5-tuple Date: Tue, 13 Feb 2018 13:35:09 -0700 Message-ID: References: <20180213000602.12150-1-dsahern@gmail.com> <20180213000602.12150-6-dsahern@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: roopa@cumulusnetworks.com, nikolay@cumulusnetworks.com, idosch@mellanox.com To: nicolas.dichtel@6wind.com, netdev@vger.kernel.org Return-path: Received: from mail-pl0-f50.google.com ([209.85.160.50]:44522 "EHLO mail-pl0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965740AbeBMUfL (ORCPT ); Tue, 13 Feb 2018 15:35:11 -0500 Received: by mail-pl0-f50.google.com with SMTP id w21so208789plp.11 for ; Tue, 13 Feb 2018 12:35:11 -0800 (PST) In-Reply-To: Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: On 2/13/18 1:31 PM, Nicolas Dichtel wrote: > Le 13/02/2018 à 01:06, David Ahern a écrit : >> Some operators prefer IPv6 path selection to use a standard 5-tuple >> hash rather than just an L3 hash with the flow the label. To that end >> add support to IPv6 for multipath hash policy 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. >> >> Signed-off-by: David Ahern >> --- > Do you plan to add the nl NETCONF support for this new sysctl? > hmmm.... doesn't exist for the current IPv4 version, but in-kernel drivers are notified. I wasn't planning on it, but it can be added.