All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CRAP in 2.4.18-pre7
Date: Sun, 27 Jan 2002 18:32:49 +0100	[thread overview]
Message-ID: <3C5439C1.6000305@evision-ventures.com> (raw)
In-Reply-To: <20020126171545.GB11344@fefe.de> <3C52E671.605FA2F3@mandrakesoft.com> <3C540A90.5020904@evision-ventures.com> <3C542FE6.7C56D6BD@mandrakesoft.com>

Jeff Garzik wrote:

>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?
>
NO not at all! The transfer is one with scp over a corssover direct link 
between two hosts.
No hub between involved.

>What is the other side configured as?
>
00:00.0 Host bridge: Intel Corp. 82440MX I/O Controller (rev 01)
00:00.2 Modem: Intel Corp.: Unknown device 7196
00:02.0 VGA compatible controller: Silicon Motion, Inc. SM720 Lynx3DM 
(rev b1)
00:06.0 Multimedia audio controller: ESS Technology ES1988 Allegro-1 
(rev 12)
00:07.0 ISA bridge: Intel Corp. 82440MX PCI to ISA Bridge (rev 01)
00:07.1 IDE interface: Intel Corp. 82440MX EIDE Controller
00:07.2 USB Controller: Intel Corp. 82440MX USB Universal Host Controller
00:07.3 Bridge: Intel Corp. 82440MX Power Management Controller
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 
(rev 10)
00:0c.0 CardBus bridge: Texas Instruments PCI1451 PC card Cardbus Controller
00:0c.1 CardBus bridge: Texas Instruments PCI1451 PC card Cardbus Controller

And works otherwise fine everywhere.

>What type of cabling?
>

CAT5 crossover nothing unusual. It's a direct link between two hosts.
Most wiredly the transfer doesn't abort or therelike. It's just getting 
absymally sloooooow.

>>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.
>
Well maybe it helps this is version 17 of the chip.



  reply	other threads:[~2002-01-27 17:33 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
2002-01-27 17:32       ` Martin Dalecki [this message]
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=3C5439C1.6000305@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=jgarzik@mandrakesoft.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.