From: Jeff Garzik <jgarzik@pobox.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
akpm@osdl.org, john.ronciak@intel.com,
ganesh.venkatesan@intel.com, cramerj@intel.com,
jesse.brandeburg@intel.com, ayyappan.veeraiyan@intel.com,
mchan@broadcom.com, davem@davemloft.net
Subject: Re: [patch 2.6.13 0/5] normalize calculations of rx_dropped
Date: Mon, 12 Sep 2005 14:53:31 -0400 [thread overview]
Message-ID: <4325CEAB.2050600@pobox.com> (raw)
In-Reply-To: <09122005104858.332@bilbo.tuxdriver.com>
John W. Linville wrote:
> Some fixes to normalize how rx_dropped is calculated. This is the
> product of a discussion on netdev on or about 18 August 2005 w/
> the subject '[RFC] stats: how to count "good" packets dropped by
> hardware?'
>
> Patches for 3c59x, e1000, e100, ixgb, and tg3 to follow.
For e.g. e1000, are we sure that packets dropped by hardware are
accounted elsewhere?
Jeff
next prev parent reply other threads:[~2005-09-12 18:53 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 ` Jeff Garzik [this message]
2005-09-12 19:14 ` [patch 2.6.13 0/5] normalize calculations of rx_dropped John W. Linville
2005-10-24 21:35 ` Ben Greear
2005-10-24 21:57 ` John W. Linville
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=4325CEAB.2050600@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=ayyappan.veeraiyan@intel.com \
--cc=cramerj@intel.com \
--cc=davem@davemloft.net \
--cc=ganesh.venkatesan@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mchan@broadcom.com \
--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).