Re: [PATCH net-next v4] net: ipv4: add support for ECMP hash policy choice
From: Stephen Hemminger <stephen@networkplumber.org>
Date: 2017-03-16 16:42:00
On Thu, 16 Mar 2017 15:28:00 +0200 Nikolay Aleksandrov [off-list ref] wrote:
quoted hunk ↗ jump to hunk
diff --git a/net/ipv4/sysctl_net_ipv4.c b/net/ipv4/sysctl_net_ipv4.c index d6880a6149ee..62c4f94923e5 100644 --- a/net/ipv4/sysctl_net_ipv4.c +++ b/net/ipv4/sysctl_net_ipv4.c@@ -1004,6 +1004,15 @@ static struct ctl_table ipv4_net_table[] = { .extra1 = &zero, .extra2 = &one, }, + { + .procname = "fib_multipath_hash_policy", + .data = &init_net.ipv4.sysctl_fib_multipath_hash_policy, + .maxlen = sizeof(int), + .mode = 0644, + .proc_handler = proc_dointvec_minmax, + .extra1 = &zero, + .extra2 = &one, +
Rather than having magic integer values, it would be better to use strings (like TCP congestion control). Especially if you want to support more values in the future. Also what about IPv6?