From: David Miller <davem@davemloft.net>
To: subramanian.vijay@gmail.com
Cc: netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH net-next] tcp: Fix bug in ofo queue pruning MIB stats
Date: Wed, 21 Dec 2011 22:15:11 -0500 (EST) [thread overview]
Message-ID: <20111221.221511.1067604757446412302.davem@davemloft.net> (raw)
In-Reply-To: <CAGK4HS8g41A8KB9iqyabZN85Ytgb+HPk3wwvoOuwkk8s9+iuCA@mail.gmail.com>
From: Vijay Subramanian <subramanian.vijay@gmail.com>
Date: Wed, 21 Dec 2011 17:14:05 -0800
> If the counter is tracking the right thing, is it worth fixing
> netstat?
Probably.
The thing is, I can see both intepretations being useful.
If we count packets, we can't tell that OFO pruning happened 4 times
vs. we pruned 4 packets.
But if you want to know the "extent" to which OFO pruning occurs, then
you want the packet count.
next prev parent reply other threads:[~2011-12-22 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 23:50 [PATCH net-next] tcp: Fix bug in ofo queue pruning MIB stats Vijay Subramanian
2011-12-22 0:33 ` David Miller
2011-12-22 1:14 ` Vijay Subramanian
2011-12-22 3:15 ` David Miller [this message]
2012-01-03 23:10 ` Rick Jones
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=20111221.221511.1067604757446412302.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=subramanian.vijay@gmail.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).