From: ET Sales <sales@etinc.com>
To: nick@snowman.net
Cc: Benjamin LaHaise <bcrl@redhat.com>,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Loosing packets with Dlink DFE-580TX and SMC 9462TX
Date: Thu, 06 Jun 2002 09:21:50 -0400 [thread overview]
Message-ID: <5.1.0.14.0.20020606091713.021f0730@mail.etinc.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0206031956150.8643-100000@ns>
At 07:56 PM 6/3/02 -0400, you wrote:
Uh..aren't those 32-bit cards? There isn't enough bus bandwidth on a 32bit
PCI bus to do gigabit, so its more likely that the cards are overrunning
their buffers....
Dennis
>There are at least some gigabit ethernet hubs on the market. How badly
>does it handle collisions?
> Nick
>
>On 3 Jun 2002, Marcus Sundberg wrote:
>
> > Benjamin LaHaise <bcrl@redhat.com> writes:
> >
> > > 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.
> >
> > 0.17, but some more testing showed that the ns83820 actually works
> > just fine during this test when using just crossover cables and
> > running at gigabit speed. The original testing was done using
> > 100Mbit hubs, so my guess would be that the 83820 chips (and/or
> > driver) doesn't handle collisions too well (which I don't have a
> > problem with, as afaik GE is always switched).
> >
> > However the DFE-580TX problems remain regardless of using a hubbed
> > or switched network.
> >
> > (As booth eepro100 and tulip-based cards works fine with the hubs
> > I'm quite certain there's nothing wrong with them.)
> >
> > //Marcud
> > --
> > ---------------------------------------+--------------------------
> > 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-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
>-
>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
next prev parent reply other threads:[~2002-06-06 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 19:01 Marcus Sundberg
2002-06-03 18:24 ` Benjamin LaHaise
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 [this message]
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=5.1.0.14.0.20020606091713.021f0730@mail.etinc.com \
--to=sales@etinc.com \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=nick@snowman.net \
/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
all inboxes | Powered by JetHome®