From: "David S. Miller" <davem@redhat.com>
To: Shirley Ma <xma@us.ibm.com>
Cc: yoshfuji@linux-ipv6.org, mashirle@us.ibm.com,
kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: [PATCH] IPv6 MIB:ipv6DefaultRouterTable
Date: Thu, 15 Jan 2004 11:38:40 -0800 [thread overview]
Message-ID: <20040115113840.4b7eb5d8.davem@redhat.com> (raw)
In-Reply-To: <OF6C177E72.62FA8BF9-ON87256E1C.006A8953@us.ibm.com>
On Thu, 15 Jan 2004 11:30:25 -0800
Shirley Ma <xma@us.ibm.com> wrote:
> I don't see any application uses these values for now, so I change them.
> It's good for kernel to provide the real MIBs information. If later on,
> some applications start to use these values, they can get the correct
> numbers without converting. Unless you can give me an broken example. :-)
Format and layout of procfs files have to stay as they are, this is just the
nature of the game.
We can create new files to present information in new ways and formats,
but I totally prefer using netlink based information gathering over making
new procfs files.
next prev parent reply other threads:[~2004-01-15 19:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 19:30 [PATCH] IPv6 MIB:ipv6DefaultRouterTable Shirley Ma
2004-01-15 19:36 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 19:38 ` David S. Miller [this message]
2004-01-15 19:53 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 19:45 ` YOSHIFUJI Hideaki / 吉藤英明
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 19:59 Shirley Ma
2004-01-15 19:09 Shirley Ma
2004-01-15 19:19 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 19:37 ` David S. Miller
2004-01-15 19:47 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 18:26 Shirley Ma
2004-01-15 18:36 ` YOSHIFUJI Hideaki / 吉藤英明
2003-11-20 0:21 IPv6 MIB:ipv6PrefixTable implementation Shirley Ma
2003-12-05 21:51 ` [PATCH] IPv6 MIB:ipv6Prefix netlink notification Shirley Ma
2003-12-05 22:57 ` David S. Miller
2004-01-15 0:22 ` [PATCH] IPv6 MIB:ipv6DefaultRouterTable Shirley Ma
2004-01-15 9:03 ` YOSHIFUJI Hideaki / 吉藤英明
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=20040115113840.4b7eb5d8.davem@redhat.com \
--to=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mashirle@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=xma@us.ibm.com \
--cc=yoshfuji@linux-ipv6.org \
/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).