From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CRAP in 2.4.18-pre7
Date: Sun, 27 Jan 2002 11:50:46 -0500 [thread overview]
Message-ID: <3C542FE6.7C56D6BD@mandrakesoft.com> (raw)
In-Reply-To: <20020126171545.GB11344@fefe.de> <3C52E671.605FA2F3@mandrakesoft.com> <3C540A90.5020904@evision-ventures.com>
Martin Dalecki wrote:
> I would like to notice that the changes in 2.4.18-pre7 to the
> tulip eth driver are apparently causing absymal performance drops
> on my version of this card. Apparently the performance is dropping
> from the expected 10MB/s to about 10kB/s. The only special
> thing about the configuration in question is the fact that it's
> a direct connection between two hosts. Well, more precisely it's
> a cross-over link between my notebook and desktop.
Are you seeing collisions?
What is the other side configured as?
What type of cabling?
> Here is an excerpt from the lspci command:
>
> 00:0b.0 Ethernet controller: Digital Equipment Corporation DECchip 21041
This is interesting considering that for most people, 21041 did not work
at all until 2.4.18-preXX tulip patches.
Jeff
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
next prev parent reply other threads:[~2002-01-27 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-26 17:15 question about sparc 64-bit user land Felix von Leitner
2002-01-26 17:24 ` Ben Collins
2002-01-26 17:25 ` Jeff Garzik
2002-01-27 14:11 ` CRAP in 2.4.18-pre7 Martin Dalecki
2002-01-27 16:50 ` Jeff Garzik [this message]
2002-01-27 17:32 ` Martin Dalecki
2002-01-27 17:53 ` root
2002-01-27 21:08 ` H. Peter Anvin
2002-01-28 12:06 ` Martin Dalecki
2002-01-28 15:37 ` H. Peter Anvin
2002-01-27 18:46 ` Michal Jaegermann
2002-01-27 21:58 ` Stephan von Krawczynski
2002-01-28 3:40 ` Michal Jaegermann
2002-01-26 18:07 ` question about sparc 64-bit user land Andreas Jaeger
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=3C542FE6.7C56D6BD@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=dalecki@evision-ventures.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.