public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: beezly@beezly.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dropped packets on SUN GEM
Date: Tue, 12 Mar 2002 15:52:38 -0800 (PST)	[thread overview]
Message-ID: <20020312.155238.21594857.davem@redhat.com> (raw)
In-Reply-To: <1015976181.2652.30.camel@monkey>
In-Reply-To: <1015974664.2652.10.camel@monkey> <20020312.151443.03370128.davem@redhat.com> <1015976181.2652.30.camel@monkey>

   From: Beezly <beezly@beezly.org.uk>
   Date: 12 Mar 2002 23:36:21 +0000

   14 packets missing.
   
   325*84  = 27300
   14*1500 = 21000
   
   Are these number relevant?

The size of GEM's receive FIFO is 20K :-)
(TX fifo is 9K)

You say you are on 100Mbit, is this to a hub at half-duplex?
That is basically the worst combination for GEM because without Pause
(even my crappy Netgear 100Mbit switches negotiate pause to on with
my GEMs) there is no way to throttle the sender so that the receive
overflow condition will not occur.

Thinking... I guess my gem_rxmac_reset() does not reset the
receive FIFO so until it is filled up and reset none of the
packets received actually make it past the card.

How does it behave with the patch below added to what you are running
right now?

--- drivers/net/sungem.c.~1~	Tue Mar 12 09:35:37 2002
+++ drivers/net/sungem.c	Tue Mar 12 15:51:05 2002
@@ -401,7 +401,11 @@
 		gp->net_stats.rx_over_errors++;
 		gp->net_stats.rx_fifo_errors++;
 
+#if 1
+		return 1;
+#else
 		ret = gem_rxmac_reset(gp);
+#endif
 	}
 
 	if (rxmac_stat & MAC_RXSTAT_ACE)


  reply	other threads:[~2002-03-12 23:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-12 23:11 Dropped packets on SUN GEM Beezly
2002-03-12 23:14 ` David S. Miller
2002-03-12 23:36   ` Beezly
2002-03-12 23:52     ` David S. Miller [this message]
2002-03-13  0:08       ` Beezly
2002-03-13  0:10         ` David S. Miller
2002-03-13  0:36           ` Beezly
2002-03-13  0:56             ` David S. Miller
2002-03-13  1:07               ` Beezly
2002-03-13  1:15                 ` David S. Miller
2002-03-13  1:24                   ` Beezly

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=20020312.155238.21594857.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=beezly@beezly.org.uk \
    --cc=linux-kernel@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