From: Lucas Nussbaum <lucas@lucas-nussbaum.net>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ne2k-pci uncorrectly detecting collisions ?
Date: Wed, 5 May 2004 15:10:06 +0200 [thread overview]
Message-ID: <20040505131006.GA3412@blop.info> (raw)
In-Reply-To: <Pine.LNX.4.53.0405050855290.16355@chaos>
On Wed, May 05, 2004 at 09:00:50AM -0400, "Richard B. Johnson" <root@chaos.analogic.com> wrote:
> > I have experienced problem with the ne2k-pci driver. The symptoms were
> > extremly poor performance with TCP. After some investigations, I believe
> > it might be caused by problems with detecting collisions.
> >
>
> But software doesn't detect collisions. It just records what
> hardware said it did. It looks like you have a 10 Mb/s card
> on a 100 Mb/s network. The collisions reported are how the
> hardware throttles the difference in physical-link speed.
The hub is a 10/100 one, and the 3 RTL8029 are 10 Mbps only.
> It is possible that software didn't initialize a 100 Mb/s
> device and instead initialized it to 10 Mb/s, but you
> don't have any evidence of that presented.
No, because RTL8029 are 10 mbps only (they are BNC/RJ45 NICs).
But what I thought was that maybe, they were initialised as full duplex,
not half duplex. But again, I don't know where I can check that. I added
some printks and determined that the code used to init them full duplex
was never used. And there's no way to force them half duplex with this
driver.
Lucas
next prev parent reply other threads:[~2004-05-05 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 12:35 ne2k-pci uncorrectly detecting collisions ? Lucas Nussbaum
2004-05-04 12:55 ` backblue
2004-05-05 13:00 ` Richard B. Johnson
2004-05-05 13:10 ` Lucas Nussbaum [this message]
2004-05-05 19:45 ` Denis Vlasenko
2004-05-06 9:52 ` Lucas Nussbaum
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=20040505131006.GA3412@blop.info \
--to=lucas@lucas-nussbaum.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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