[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <beb58830-de0e-cb47-0a5c-6109be737fb5@gmail.com>
Date: Mon, 3 May 2021 20:40:18 -0600
From: David Ahern <dsahern@...il.com>
To: Ido Schimmel <idosch@...sch.org>, netdev@...r.kernel.org
Cc: davem@...emloft.net, kuba@...nel.org, petrm@...dia.com,
roopa@...dia.com, nikolay@...dia.com, ssuryaextr@...il.com,
mlxsw@...dia.com, Ido Schimmel <idosch@...dia.com>
Subject: Re: [RFC PATCH net-next 03/10] ipv4: Add custom multipath hash policy
On 5/3/21 8:38 PM, David Ahern wrote:
> On 5/2/21 10:22 AM, Ido Schimmel wrote:
>> diff --git a/Documentation/networking/ip-sysctl.rst b/Documentation/networking/ip-sysctl.rst
>> index 8ab61f4edf02..549601494694 100644
>> --- a/Documentation/networking/ip-sysctl.rst
>> +++ b/Documentation/networking/ip-sysctl.rst
>> @@ -99,6 +99,8 @@ fib_multipath_hash_policy - INTEGER
>> - 0 - Layer 3
>> - 1 - Layer 4
>> - 2 - Layer 3 or inner Layer 3 if present
>> + - 3 - Custom multipath hash. Fields used for multipath hash calculation
>> + are determined by fib_multipath_hash_fields sysctl
>>
>
> If you default the fields to L3, then seems like the custom option is a
> more generic case of '0'.
>
Actually this is the more generic case of all of them, so all of them
could be implemented using this custom field selection.
Powered by blists - more mailing lists