From: Benjamin LaHaise <bcrl@redhat.com>
To: Marcus Sundberg <marcus@ingate.com>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Loosing packets with Dlink DFE-580TX and SMC 9462TX
Date: Mon, 3 Jun 2002 14:24:24 -0400 [thread overview]
Message-ID: <20020603142424.A29676@redhat.com> (raw)
In-Reply-To: <ved6vepylg.fsf@inigo.ingate.se>
What version of ns83820.c are you using? Version 0.17 of ns83820.c
made significant improvements under load. Other possibilities include
cabling problems (watch the kernel logs for changes in link state).
Try to find out where the packets are getting dropped by looking
through /proc/net/snmp and other statistics counters in the kernel.
-ben
On Wed, May 29, 2002 at 09:01:47PM +0200, Marcus Sundberg wrote:
> Hi,
>
> I'm seeing severe packet-loss with two different types of network
> cards:
> D-link DFE-580TX (DL10050B aka OEM:ed Sundance ST201 chip) and
> SMC 9462TX (NS83820 chip)
>
> The machine is an Athlon XP1800+ with VIA KT266 chipset and what
> I'm doing is to send several bi-directional streams of small UDP
> packets through the machine. Each stream consists of 50 UDP
> packets per second in each direction, with 200 bytes payload.
>
> Using either Intel 21143 based cards (tulip driver) or Intel 82559
> (eepro100 driver) I can send 100 such streams through the machine
> with no packet loss (the load generators starts walking on their
> knees a bit over 100). This equals 10000 packets/second or about
> 19 Mbit/s.
>
> However using either the Dlink cards or the SMC cards I start getting
> severe packet loss at between 50 and 70 streams. After fixing the
> sundance driver so it doesn't turn off interrupts for 3.2ms whenever
> the boguscnt counter in the interrupt handler happens to reach zero
> I can't find anything particularly bad neither in the driver nor
> in the ST201 chip spec, but packets keep getting dropped.
> (The 83820-driver I haven't looked at at all)
>
> Before digging further into this I'd like to know if anyone have
> had similiar problems, or are using any of these cards/drivers
> without problems, or have an idea if it is the chips or the drivers
> which are broken? Or can just tell me whether these cards are
> exceptionally bad or if eepro100/tulip are exceptionally good?
>
> I migh also take the opportunity to ask if anyone can recommend
> another 4-port (or more) 100Mbit ethernet card than the DFE-580TX?
>
> //Marcus
> --
> ---------------------------------------+--------------------------
> Marcus Sundberg <marcus@ingate.com> | Firewalls with SIP & NAT
> Firewall Developer, Ingate Systems AB | http://www.ingate.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
"You will be reincarnated as a toad; and you will be much happier."
next prev parent reply other threads:[~2002-06-03 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 19:01 Loosing packets with Dlink DFE-580TX and SMC 9462TX Marcus Sundberg
2002-06-03 18:24 ` Benjamin LaHaise [this message]
2002-06-03 19:20 ` Marcus Sundberg
2002-06-03 23:56 ` nick
2002-06-04 4:05 ` Donald Becker
2002-06-06 13:21 ` ET Sales
2002-06-06 22:47 ` Benjamin LaHaise
2002-06-07 6:24 ` Ben Greear
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=20020603142424.A29676@redhat.com \
--to=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=marcus@ingate.com \
/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