From: "John W. Linville" <linville@tuxdriver.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [patch 2.6.13 0/5] normalize calculations of rx_dropped
Date: Mon, 24 Oct 2005 17:57:53 -0400 [thread overview]
Message-ID: <20051024215751.GH28212@tuxdriver.com> (raw)
In-Reply-To: <435D53AE.3020401@candelatech.com>
On Mon, Oct 24, 2005 at 02:35:42PM -0700, Ben Greear wrote:
> It doesn't matter too much to me either way, but I'd like for there to
> be a precisely documented definition for the various net-stats so that
> I can correctly show the values to user-space (I can certainly add
> rx_discards
> to rx_errors for a 'total rx errors' value, but I need to know whether
> rx_discards is already in rx_errors to keep from counting things twice.)
My opinion is that:
-- rx_errors should count all "on the wire" hardware errors;
-- rx_missed_errors should count frames w/ no "on the wire"
errors that cannot be received by the hardware (generally
due to lack of DMA bufers); and,
-- rx_discards should count frames dropped by the kernel
after successful reception by the hardware.
I do _not_ think rx_missed_errors should be counted as part of
rx_errors, but I could be persuaded otherwise.
> Jeff: Could you lay down the law somewhere in the Documentation/
> directory and then let us start fixing any driver that does it differently?
It does seem like a netdev stats clarification doc would be
appropriate. Does anyone have the beginnings of this?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2005-10-24 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050822181726.GJ2736@tuxdriver.com>
2005-09-12 14:48 ` [patch 2.6.13 0/5] normalize calculations of rx_dropped John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 1/5] 3c59x: correct rx_dropped counting John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 2/5] e1000: " John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 3/5] e100: correct rx_dropped and add rx_missed_errors John W. Linville
2005-09-12 14:49 ` [patch 2.6.13 4/5] ixgb: correct rx_dropped counting John W. Linville
2005-09-12 14:49 ` [patch 2.6.13 5/5] tg3: correct rx_dropped and add rx_missed_errors John W. Linville
2005-09-12 18:53 ` [patch 2.6.13 0/5] normalize calculations of rx_dropped Jeff Garzik
2005-09-12 19:14 ` John W. Linville
2005-10-24 21:35 ` Ben Greear
2005-10-24 21:57 ` John W. Linville [this message]
2005-10-25 1:15 ` Ben Greear
2005-10-25 1:42 ` jamal
2005-10-25 19:50 ` Ingo Oeser
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=20051024215751.GH28212@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=greearb@candelatech.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.