[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180110.151501.2071855954960334867.davem@davemloft.net>
Date: Wed, 10 Jan 2018 15:15:01 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: idosch@...lanox.com
Cc: netdev@...r.kernel.org, dsahern@...il.com,
roopa@...ulusnetworks.com, nikolay@...ulusnetworks.com,
pch@...bogen.com, jkbs@...hat.com, yoshfuji@...ux-ipv6.org,
mlxsw@...lanox.com
Subject: Re: [PATCH net-next 0/4] ipv6: Add support for non-equal-cost
multipath
From: Ido Schimmel <idosch@...lanox.com>
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!
Powered by blists - more mailing lists