From: Eric Dumazet <dada1@cosmosbay.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] snmp: add missing counters for RFC 4293
Date: Wed, 22 Apr 2009 07:15:15 +0200 [thread overview]
Message-ID: <49EEA7E3.3080507@cosmosbay.com> (raw)
In-Reply-To: <20090422011214.GA18856@localhost.localdomain>
Neil Horman a écrit :
> Hey all-
> New patch, taking Erics commentary pointing out my prior stupidity into
> account :).
>
>
> The IP MIB (RFC 4293) defines stats for InOctets, OutOctets, InMcastOctets and
> OutMcastOctets:
> http://tools.ietf.org/html/rfc4293
> But it seems we don't track those in any way that easy to separate from other
> protocols. This patch adds those missing counters to the stats file. Tested
> successfully by me
Well, looking now at the patch again, I think you cannot add new fields
without breaking existing apps. My previous review stoped at this _BH thing
wihthout looking further :)
Also, it seems some RFC4293 items are already handled, since commit d831666e
from Mitsuru Chinen. Check net/ipv4/proc.c, line 114
/* Following RFC4293 items are displayed in /proc/net/netstat */
static const struct snmp_mib snmp4_ipextstats_list[] = {
SNMP_MIB_ITEM("InNoRoutes", IPSTATS_MIB_INNOROUTES),
SNMP_MIB_ITEM("InTruncatedPkts", IPSTATS_MIB_INTRUNCATEDPKTS),
SNMP_MIB_ITEM("InMcastPkts", IPSTATS_MIB_INMCASTPKTS),
SNMP_MIB_ITEM("OutMcastPkts", IPSTATS_MIB_OUTMCASTPKTS),
SNMP_MIB_ITEM("InBcastPkts", IPSTATS_MIB_INBCASTPKTS),
SNMP_MIB_ITEM("OutBcastPkts", IPSTATS_MIB_OUTBCASTPKTS),
SNMP_MIB_SENTINEL
};
# grep IpExt /proc/net/netstat
IpExt: InNoRoutes InTruncatedPkts InMcastPkts OutMcastPkts InBcastPkts OutBcastPkts
IpExt: 0 0 0 0 5089 0
So you might add items after existing ones, in IpExt preferably, in order not
breaking old applications.
Thanks
next prev parent reply other threads:[~2009-04-22 5:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 19:39 [PATCH] snmp: add missing counters for RFC 4293 Neil Horman
2009-04-21 19:58 ` Eric Dumazet
2009-04-21 20:09 ` Neil Horman
2009-04-21 20:45 ` Eric Dumazet
2009-04-21 23:03 ` Neil Horman
2009-04-22 1:12 ` Neil Horman
2009-04-22 5:15 ` Eric Dumazet [this message]
2009-04-22 9:08 ` David Miller
2009-04-22 9:35 ` Eric Dumazet
2009-04-22 9:50 ` David Miller
2009-04-22 10:53 ` Neil Horman
2009-04-22 16:50 ` Neil Horman
2009-04-22 17:39 ` Eric Dumazet
2009-04-22 18:44 ` Neil Horman
2009-04-23 15:28 ` Neil Horman
2009-04-23 16:37 ` Eric Dumazet
2009-04-23 16:56 ` Neil Horman
2009-04-23 17:13 ` Eric Dumazet
2009-04-23 17:25 ` Neil Horman
2009-04-23 17:32 ` Eric Dumazet
2009-04-23 18:28 ` Neil Horman
2009-04-24 14:10 ` Eric Dumazet
2009-04-24 17:06 ` Neil Horman
2009-04-24 18:37 ` Neil Horman
2009-04-27 9:45 ` David Miller
2009-04-22 5:17 ` 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=49EEA7E3.3080507@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.