[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAEUsAPafiEMsvrL6y7RUNv-z=-HUJvdi0O2aQuHHDV4mkRkZjg@mail.gmail.com>
Date: Wed, 25 Feb 2015 00:02:45 -0600
From: Chris Rorvick <chris@...vick.com>
To: David Miller <davem@...emloft.net>
Cc: kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org,
kaber@...sh.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fib_trie: Add proc entry for next-hop exceptions
On Tue, Feb 24, 2015 at 11:33 PM, David Miller <davem@...emloft.net> wrote:
> From: Chris Rorvick <chris@...vick.com>
> Date: Tue, 24 Feb 2015 23:27:12 -0600
>
>> Exceptions are added to the FIB in response to ICMP redirects and to
>> account for PMTU, but there is little visibility into what the current
>> exceptions are. Add a proc entry for listing the current next-hop
>> exceptions
>>
>> Signed-off-by: Chris Rorvick <chris@...vick.com>
>
> Procfs exportation of networking information is deprecated.
>
> New pieces of information should be provided via netlink.
Ah, OK. So is the premise of this patch still interesting or am I
just ignorant? It seems like knowing whether or not you're
accumulating a lot of exceptions is interesting and I could not figure
out how to do that.
Thanks for the feedback.
Regards,
Chris
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists