[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170316094152.0ac70537@xeon-e3>
Date: Thu, 16 Mar 2017 09:41:52 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net,
roopa@...ulusnetworks.com, dsa@...ulusnetworks.com,
jkbs@...hat.com, edumazet@...gle.com, pch@...bogen.com,
nicolas.dichtel@...nd.com
Subject: Re: [PATCH net-next v4] net: ipv4: add support for ECMP hash policy
choice
On Thu, 16 Mar 2017 15:28:00 +0200
Nikolay Aleksandrov <nikolay@...ulusnetworks.com> wrote:
> 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?
Powered by blists - more mailing lists