From: "John W. Linville" <linville@tuxdriver.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: john.ronciak@intel.com, ganesh.venkatesan@intel.com,
jesse.brandeburg@intel.com, jgarzik@pobox.com
Subject: [patch 2.6.13 3/5] e100: correct rx_dropped and add rx_missed_errors
Date: Mon, 12 Sep 2005 10:48:59 -0400 [thread overview]
Message-ID: <09122005104859.522@bilbo.tuxdriver.com> (raw)
In-Reply-To: <09122005104859.453@bilbo.tuxdriver.com>
Do not count non-error frames dropped by the hardware as
part of rx_dropped. Instead, count those frames dropped as
rx_missed_errors. Also, do not count other error frames as part of
rx_dropped. Finally, do not count oversized frames in rx_dropped
(since they are counted as part of rx_length_errors).
Signed-off-by: John W. Linville <linville@tuxdriver.com>
---
drivers/net/e100.c | 4 +---
1 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/net/e100.c b/drivers/net/e100.c
--- a/drivers/net/e100.c
+++ b/drivers/net/e100.c
@@ -1387,13 +1387,13 @@ static void e100_update_stats(struct nic
ns->collisions += nic->tx_collisions;
ns->tx_errors += le32_to_cpu(s->tx_max_collisions) +
le32_to_cpu(s->tx_lost_crs);
- ns->rx_dropped += le32_to_cpu(s->rx_resource_errors);
ns->rx_length_errors += le32_to_cpu(s->rx_short_frame_errors) +
nic->rx_over_length_errors;
ns->rx_crc_errors += le32_to_cpu(s->rx_crc_errors);
ns->rx_frame_errors += le32_to_cpu(s->rx_alignment_errors);
ns->rx_over_errors += le32_to_cpu(s->rx_overrun_errors);
ns->rx_fifo_errors += le32_to_cpu(s->rx_overrun_errors);
+ ns->rx_missed_errors += le32_to_cpu(s->rx_resource_errors);
ns->rx_errors += le32_to_cpu(s->rx_crc_errors) +
le32_to_cpu(s->rx_alignment_errors) +
le32_to_cpu(s->rx_short_frame_errors) +
@@ -1727,12 +1727,10 @@ static inline int e100_rx_indicate(struc
if(unlikely(!(rfd_status & cb_ok))) {
/* Don't indicate if hardware indicates errors */
- nic->net_stats.rx_dropped++;
dev_kfree_skb_any(skb);
} else if(actual_size > ETH_DATA_LEN + VLAN_ETH_HLEN) {
/* Don't indicate oversized frames */
nic->rx_over_length_errors++;
- nic->net_stats.rx_dropped++;
dev_kfree_skb_any(skb);
} else {
nic->net_stats.rx_packets++;
next prev parent reply other threads:[~2005-09-12 14:48 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 ` John W. Linville [this message]
2005-09-12 14:49 ` [patch 2.6.13 4/5] ixgb: " 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
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=09122005104859.522@bilbo.tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ganesh.venkatesan@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jgarzik@pobox.com \
--cc=john.ronciak@intel.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 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).