[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170315082023.2a976f0b@xeon-e3>
Date: Wed, 15 Mar 2017 08:20:23 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: David Ahern <dsa@...ulusnetworks.com>
Cc: nicolas.dichtel@...nd.com,
Roopa Prabhu <roopa@...ulusnetworks.com>,
David Miller <davem@...emloft.net>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>, jkbs@...hat.com,
Eric Dumazet <edumazet@...gle.com>,
Peter Christensen <pch@...bogen.com>
Subject: Re: [PATCH net-next v3] net: ipv4: add support for ECMP hash policy
choice
On Wed, 15 Mar 2017 09:01:16 -0600
David Ahern <dsa@...ulusnetworks.com> wrote:
> On 3/15/17 3:17 AM, Nicolas Dichtel wrote:
> >>> Is there another patch to add the NETCONFA_ECMP support?
> >>>
> >>
> >> does userspace care?
> > Yes, I think it is needed so that userspace can correctly monitor this behavior.
> > It also enables to check this parameter through netlink.
> >
>
> I don't understand why userspace cares. What can userspace do with that
> information?
There are cases such as routing or switch control from userspace where the desire
is to track kernel behavior in an external program. I know of at least 3 cases where
this is done.
Powered by blists - more mailing lists