From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: nicolas.dichtel@6wind.com,
Roopa Prabhu <roopa@cumulusnetworks.com>,
David Miller <davem@davemloft.net>,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
jkbs@redhat.com, Eric Dumazet <edumazet@google.com>,
Peter Christensen <pch@ordbogen.com>
Subject: Re: [PATCH net-next v3] net: ipv4: add support for ECMP hash policy choice
Date: Wed, 15 Mar 2017 08:20:23 -0700 [thread overview]
Message-ID: <20170315082023.2a976f0b@xeon-e3> (raw)
In-Reply-To: <5c0b73c5-ee6b-d67f-b01e-0d749c8ced6d@cumulusnetworks.com>
On Wed, 15 Mar 2017 09:01:16 -0600
David Ahern <dsa@cumulusnetworks.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.
next prev parent reply other threads:[~2017-03-15 15:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 14:59 [PATCH net-next] net: ipv4: add support for ECMP hash policy choice Nikolay Aleksandrov
2017-03-06 16:24 ` David Ahern
2017-03-06 16:52 ` Nikolay Aleksandrov
2017-03-07 6:16 ` Roopa Prabhu
2017-03-07 11:01 ` [PATCH net-next v2] " Nikolay Aleksandrov
2017-03-08 12:05 ` Jakub Sitnicki
2017-03-08 12:43 ` Nikolay Aleksandrov
2017-03-08 16:00 ` Jakub Sitnicki
2017-03-13 2:23 ` David Miller
2017-03-14 15:36 ` [PATCH net-next v3] " Nikolay Aleksandrov
2017-03-14 15:55 ` Stephen Hemminger
2017-03-14 15:58 ` Nikolay Aleksandrov
2017-03-14 18:48 ` David Miller
2017-03-14 20:25 ` Stephen Hemminger
2017-03-14 21:10 ` Roopa Prabhu
2017-03-14 21:42 ` Stephen Hemminger
2017-03-14 22:38 ` Roopa Prabhu
2017-03-14 23:27 ` Stephen Hemminger
2017-03-14 23:45 ` David Ahern
2017-03-15 9:17 ` Nicolas Dichtel
2017-03-15 10:46 ` Nikolay Aleksandrov
2017-03-15 11:18 ` Nicolas Dichtel
2017-03-15 11:27 ` Nikolay Aleksandrov
2017-03-15 15:01 ` David Ahern
2017-03-15 15:20 ` Stephen Hemminger [this message]
2017-03-15 0:24 ` David Miller
2017-03-15 2:30 ` Tom Herbert
2017-03-17 3:36 ` David Miller
2017-03-14 18:55 ` Nikolay Aleksandrov
2017-03-15 11:32 ` Jakub Sitnicki
2017-03-15 12:10 ` Nikolay Aleksandrov
2017-03-16 13:28 ` [PATCH net-next v4] " Nikolay Aleksandrov
2017-03-16 16:41 ` Stephen Hemminger
2017-03-16 16:49 ` Nikolay Aleksandrov
2017-03-17 10:06 ` Nikolay Aleksandrov
2017-03-21 22:28 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170315082023.2a976f0b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=edumazet@google.com \
--cc=jkbs@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=nikolay@cumulusnetworks.com \
--cc=pch@ordbogen.com \
--cc=roopa@cumulusnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).