Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752353AbbBYGCr (ORCPT ); Wed, 25 Feb 2015 01:02:47 -0500 Received: from mail-qc0-f173.google.com ([209.85.216.173]:43531 "EHLO mail-qc0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750764AbbBYGCq (ORCPT ); Wed, 25 Feb 2015 01:02:46 -0500 MIME-Version: 1.0 In-Reply-To: <20150225.003305.1943185648487924578.davem@davemloft.net> References: <1424842032-3151-1-git-send-email-chris@rorvick.com> <20150225.003305.1943185648487924578.davem@davemloft.net> Date: Wed, 25 Feb 2015 00:02:45 -0600 X-Google-Sender-Auth: TL2dDf0O-dexMu7bRR2n2CStHpo Message-ID: Subject: Re: [PATCH] fib_trie: Add proc entry for next-hop exceptions From: Chris Rorvick To: David Miller Cc: kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1078 Lines: 30 On Tue, Feb 24, 2015 at 11:33 PM, David Miller wrote: > From: Chris Rorvick > 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 > > 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 linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/