From: Varun Chandramohan <varunc@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: yoshfuji@linux-ipv6.org, netdev@vger.kernel.org, sri@us.ibm.com,
dlstevens@us.ibm.com, varuncha@in.ibm.com
Subject: Re: [PATCH] Age Entry For IPv4 Route Table
Date: Mon, 25 Jun 2007 13:28:37 +0530 [thread overview]
Message-ID: <467F75AD.1090004@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070625.003208.69400937.davem@davemloft.net>
David Miller wrote:
> From: Varun Chandramohan <varunc@linux.vnet.ibm.com>
> Date: Mon, 25 Jun 2007 10:51:39 +0530
>
>
>> YOSHIFUJI Hideaki / ������������ wrote:
>>
>>> In article <20070625102838.9d1fee20.varunc@linux.vnet.ibm.com> (at Mon, 25 Jun 2007 10:28:38 +0530), Varun Chandramohan <varunc@linux.vnet.ibm.com> says:
>>>
>>>
>>>
>>>> According to the RFC 4292 (IP Forwarding Table MIB) there is a need for an age entry for all the routes in the routing table. The entry in the RFC is inetCidrRouteAge and oid is inetCidrRouteAge.1.10.
>>>> Many snmp application require this age entry. So iam adding the age field in the routing table and providing
>>>> the interface for this value via /proc/net/route.
>>>>
>>>>
>>> I'm not in favor of adding new field(s) to /proc/net/route.
>>>
>>>
>>>
>> Do you think it will break any user level functionality? I have tested
>> with netstat, route and net-snmp which reads from the same /proc
>> interface. They seem to work fine.
>>
>
> You can't change procfs file output format, someone's shell scripts
> or whatever out there will break. Just testing some common packages
> isn't a way to be able to change procfs file output, it's a user
> exported API and just like system calls you cannot change them.
>
>
Hi Dave,
Ok i understand. But can you suggest anyother way to do the above?
Regards,
Varun
next prev parent reply other threads:[~2007-06-25 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 4:58 [PATCH] Age Entry For IPv4 Route Table Varun Chandramohan
2007-06-25 5:14 ` YOSHIFUJI Hideaki / 吉藤英明
2007-06-25 5:21 ` Varun Chandramohan
[not found] ` <20070625.003208.69400937.davem@davemloft.net>
2007-06-25 7:58 ` Varun Chandramohan [this message]
2007-06-25 8:42 ` David Miller
2007-06-25 14:10 ` Eric Dumazet
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=467F75AD.1090004@linux.vnet.ibm.com \
--to=varunc@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.com \
--cc=varuncha@in.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).