From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next 0/4] ipv6: Add support for non-equal-cost multipath Date: Wed, 10 Jan 2018 15:15:01 -0500 (EST) Message-ID: <20180110.151501.2071855954960334867.davem@davemloft.net> References: <20180109144028.30133-1-idosch@mellanox.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, dsahern@gmail.com, roopa@cumulusnetworks.com, nikolay@cumulusnetworks.com, pch@ordbogen.com, jkbs@redhat.com, yoshfuji@linux-ipv6.org, mlxsw@mellanox.com To: idosch@mellanox.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:54628 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751396AbeAJUPD (ORCPT ); Wed, 10 Jan 2018 15:15:03 -0500 In-Reply-To: <20180109144028.30133-1-idosch@mellanox.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Ido Schimmel Date: Tue, 9 Jan 2018 16:40:24 +0200 > This set aims to add support for IPv6 non-equal-cost multipath routes. > The first three patches convert multipath selection to use the > hash-threshold method (RFC 2992) instead of modulo-N. The same method is > employed by the IPv4 routing code since commit 0e884c78ee19 ("ipv4: L3 > hash-based multipath"). > > Unlike modulo-N, with hash-threshold only the flows near the region > boundaries are affected when a nexthop is added or removed. In addition, > it allows us to easily add support for non-equal-cost multipath in the > last patch by sizing the different regions according to the provided > weights. This looks great, series applied, thanks!