[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <59331028-c1a5-2a7a-1e27-57e62f95030f@gmail.com>
Date: Tue, 11 May 2021 09:10:46 -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 v2 02/10] ipv4: Add a sysctl to control
multipath hash fields
On 5/9/21 9:16 AM, Ido Schimmel wrote:
> diff --git a/Documentation/networking/ip-sysctl.rst b/Documentation/networking/ip-sysctl.rst
> index c2ecc9894fd0..15982f830abc 100644
> --- a/Documentation/networking/ip-sysctl.rst
> +++ b/Documentation/networking/ip-sysctl.rst
> @@ -100,6 +100,33 @@ fib_multipath_hash_policy - INTEGER
> - 1 - Layer 4
> - 2 - Layer 3 or inner Layer 3 if present
>
> +fib_multipath_hash_fields - UNSIGNED INTEGER
> + When fib_multipath_hash_policy is set to 3 (custom multipath hash), the
> + fields used for multipath hash calculation are determined by this
> + sysctl.
> +
> + This value is a bitmask which enables various fields for multipath hash
> + calculation.
> +
> + Possible fields are:
> +
> + ====== ============================
> + 0x0001 Source IP address
> + 0x0002 Destination IP address
> + 0x0004 IP protocol
> + 0x0008 Unused
Document that this bit is flowlabel for IPv6 and ignored for ipv4.
Powered by blists - more mailing lists