From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com ([66.111.4.29]:51639 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1424338AbeCBNwo (ORCPT ); Fri, 2 Mar 2018 08:52:44 -0500 Date: Fri, 2 Mar 2018 15:52:40 +0200 From: Ido Schimmel To: David Ahern Cc: netdev@vger.kernel.org, davem@davemloft.net, roopa@cumulusnetworks.com, nikolay@cumulusnetworks.com, tom@herbertland.com Subject: Re: [PATCH v2 net-next 07/10] net/ipv6: Add support for path selection using hash of 5-tuple Message-ID: <20180302135240.GG23979@splinter> References: <20180302032950.21154-1-dsahern@gmail.com> <20180302032950.21154-8-dsahern@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180302032950.21154-8-dsahern@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Mar 01, 2018 at 07:29:47PM -0800, David Ahern wrote: > 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 Reviewed-by: Ido Schimmel Tested-by: Ido Schimmel