From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/4] fib_trie: improve output format for /proc/net/fib_trie
Date: Tue, 12 Feb 2008 19:23:59 -0800 [thread overview]
Message-ID: <47B262CF.9040407@vyatta.com> (raw)
In-Reply-To: <20080212182823.6f8a3a12.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Tue, 12 Feb 2008 16:50:44 -0800 Stephen Hemminger <shemminger@vyatta.com> wrote:
>
>
>> Make output format prettier (more tree like).
>>
>> <local>:
>> --- 0.0.0.0/0
>> |--- 10.111.111.0/24
>> | +-- 10.111.111.0/32 link broadcast
>> | |--- 10.111.111.254/31
>> | | +-- 10.111.111.254/32 host local
>> | | +-- 10.111.111.255/32 link broadcast
>> |--- 127.0.0.0/8
>> | |--- 127.0.0.0/31
>> | | +-- 127.0.0.0/32 link broadcast
>> | | +-- 127.0.0.0/8 host local
>> | | +-- 127.0.0.1/32 host local
>> | +-- 127.255.255.255/32 link broadcast
>> |--- 192.168.1.0/24
>> | |--- 192.168.1.0/28
>> | | +-- 192.168.1.0/32 link broadcast
>> | | +-- 192.168.1.9/32 host local
>> | +-- 192.168.1.255/32 link broadcast
>> <main>:
>> --- 0.0.0.0/0
>> |--- 0.0.0.0/4
>> | +-- 0.0.0.0/0 universe unicast
>> | +-- 10.111.111.0/24 link unicast
>> +-- 169.254.0.0/16 link unicast
>> +-- 192.168.1.0/24 link unicast
>>
>
> isn't that a non-back-compatible kernel ABI change? It might
> break pre-existing parsers?
>
>
Fib trie was always experimental and the output format was intended to
be tree like
but was broken. There are no known parsers of fib trie, and I think
Vyatta will probably
be the first distro to ship with it enabled.
> aside: how lame are we to put pretty-printers in the kernel?
> English-only ones, at that? Root cause: kernel developers still
> don't have a sufficiently easy way of shipping userspace tools.
Agreed, the structure of the trie doesn't come out via netlink (only the
addresses).
next prev parent reply other threads:[~2008-02-13 3:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080213005042.150212716@vyatta.com>
2008-02-13 0:50 ` [PATCH 1/4] rcu_assign_pointer: null check fix Stephen Hemminger
2008-02-13 1:27 ` David Miller
2008-02-13 8:07 ` Jarek Poplawski
2008-02-13 0:50 ` [PATCH 2/4] fib_trie: improve output format for /proc/net/fib_trie Stephen Hemminger
2008-02-13 2:28 ` Andrew Morton
2008-02-13 3:23 ` Stephen Hemminger [this message]
[not found] ` <20080213005122.879352336@vyatta.com>
2008-02-13 1:26 ` [PATCH 4/4] hlist_for_each_entry_continue simplification 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=47B262CF.9040407@vyatta.com \
--to=stephen.hemminger@vyatta.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).