From: Varun Chandramohan <varunc@linux.vnet.ibm.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, kaber@trash.net, socketcan@hartkopp.net,
shemminger@linux-foundation.org, krkumar2@in.ibm.com,
tgraf@suug.ch, varuncha@in.ibm.com
Subject: [RESEND][PATCH 0/4 Rev-3] Age Entry For IPv4 & IPv6 Route Table
Date: Wed, 19 Sep 2007 09:23:18 +0530 [thread overview]
Message-ID: <20070919092318.949372eb.varunc@linux.vnet.ibm.com> (raw)
Hi Dave,
Iam resending the patch set again. Let me know if you need anything else.
Regards,
Varun
Original Comment:
According to the RFC 4292 (IP Forwarding Table MIB) there is a need for an age entry for all the routes in therouting 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 for ipv4 and ipv6 and providing the interface for this value netlink.
I made a note of changes i made as per the suggestions given in the community. Here is the changelog.
Changelog since ver 1:
---------------------
Changes Suggestion
1)Change in the interface from proc to netlink.
It was not approved by David Miller and Yoshifuji. David Miller & Yoshifuji
2)Change from jiffies to timeval. Eric Dumazet
3)Rounding up timeval Patrick McHardy, Oliver Hartkopp
Eric Dumazet.
4)Relocate timeval_to_sec Stephen Hemminger, Krishna Kumar
5)Using macro RT6_GET_ROUTE_INFO Krishna Kumar
6)Add proper comment for timeval_to_sec Eric Dumazet
7)Add proper comment for timeval insertion Thomas Graf
Signed-off-by: Varun Chandramohan <varunc@linux.vnet.ibm.com>
---
reply other threads:[~2007-09-19 3:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070919092318.949372eb.varunc@linux.vnet.ibm.com \
--to=varunc@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=krkumar2@in.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=socketcan@hartkopp.net \
--cc=tgraf@suug.ch \
--cc=varuncha@in.ibm.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).