From: Patrick McHardy <kaber@trash.net>
To: Milan Kocian <milon@wq.cz>
Cc: netdev@vger.kernel.org
Subject: Re: Difference between device statistics from ifconfig and ip -s l l
Date: Wed, 17 Oct 2007 12:35:43 +0200 [thread overview]
Message-ID: <4715E57F.6080905@trash.net> (raw)
In-Reply-To: <20071017101303.GB16356@wq.cz>
Milan Kocian wrote:
> On Wed, Oct 17, 2007 at 11:36:30AM +0200, Patrick McHardy wrote:
>
>> ifconfig gets its data from /proc/net/dev, which adds up rx_errors
>> and rx_missed.
>>
>
> Adds up rx_errors and rx_missed and prints it as dropped ? Ok, ifconfig is
> a little old. But why I don't see missed packets from RX errors detailed stats
> (ip -s -s l l) in non-detailed stats as errors and see zero ?
I meant to write "adds up rx_dropped and rx_missed".
next prev parent reply other threads:[~2007-10-17 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 9:27 Difference between device statistics from ifconfig and ip -s l l Milan Kocian
2007-10-17 9:36 ` Patrick McHardy
2007-10-17 10:13 ` Milan Kocian
2007-10-17 10:35 ` Patrick McHardy [this message]
2007-10-17 11:29 ` Milan Kocian
2007-10-17 12:01 ` jamal
2007-10-17 13:42 ` Milan Kocian
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=4715E57F.6080905@trash.net \
--to=kaber@trash.net \
--cc=milon@wq.cz \
--cc=netdev@vger.kernel.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).