[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <471f66fb-8f1e-bddb-7d01-1f274d24ce71@gmail.com>
Date: Tue, 13 Feb 2018 14:02:24 -0700
From: David Ahern <dsahern@...il.com>
To: nicolas.dichtel@...nd.com, netdev@...r.kernel.org
Cc: roopa@...ulusnetworks.com, nikolay@...ulusnetworks.com,
idosch@...lanox.com
Subject: Re: [PATCH RFC net-next 5/7] net/ipv6: Add support for path selection
using hash of 5-tuple
On 2/13/18 1:59 PM, Nicolas Dichtel wrote:
> Le 13/02/2018 à 21:35, David Ahern a écrit :
>> 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 <dsahern@...il.com>
>>>> ---
>>> 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.
>>
> Right for ipv4, it was on my todo list ;-)
>
Awesome, then ipv6 is a 1-liner after you add ipv4 support. :-)
Powered by blists - more mailing lists