public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Beezly <beezly@beezly.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dropped packets on SUN GEM
Date: 13 Mar 2002 00:08:47 +0000	[thread overview]
Message-ID: <1015978127.2653.49.camel@monkey> (raw)
In-Reply-To: <20020312.155238.21594857.davem@redhat.com>
In-Reply-To: <1015974664.2652.10.camel@monkey> <20020312.151443.03370128.davem@redhat.com> <1015976181.2652.30.camel@monkey>  <20020312.155238.21594857.davem@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]

On Tue, 2002-03-12 at 23:52, David S. Miller wrote:
> 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?
> 

The problem appears to get worse;

$ ping -s 1472 -i 0.1 10.0.0.3 
<snip>
1480 bytes from 10.0.0.3: icmp_seq=4487 ttl=255 time=4.13 ms
1480 bytes from 10.0.0.3: icmp_seq=4488 ttl=255 time=4.13 ms
1480 bytes from 10.0.0.3: icmp_seq=4489 ttl=255 time=4.13 ms
1480 bytes from 10.0.0.3: icmp_seq=4490 ttl=255 time=4.13 ms
1480 bytes from 10.0.0.3: icmp_seq=4491 ttl=255 time=4.14 ms
1480 bytes from 10.0.0.3: icmp_seq=4517 ttl=255 time=4.18 ms
1480 bytes from 10.0.0.3: icmp_seq=4518 ttl=255 time=4.13 ms
1480 bytes from 10.0.0.3: icmp_seq=4519 ttl=255 time=4.12 ms
1480 bytes from 10.0.0.3: icmp_seq=4520 ttl=255 time=4.13 ms

25 lost packets :(

Also, just to clarify (i wasn't clear earlier), this host is connected
via 1000Mbps full-duplex fibre to the switch.

The other machines on the switch are connected either by 100Mbps copper
or 10Mpbs copper. I'm guessing the other machines shouldn't be able to
flood the RX on this host even if they all transmitted at the same time?
(there are only three of them)

Beezly

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-03-13  0:09 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
2002-03-13  0:08       ` Beezly [this message]
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=1015978127.2653.49.camel@monkey \
    --to=beezly@beezly.org.uk \
    --cc=davem@redhat.com \
    --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