From: "Allen Curtis" <acurtis@onz.com>
To: "Conn Clark" <clark@esteem.com>
Cc: "May Ling List" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Poor 8260 FCC Ethernet performance
Date: Fri, 31 May 2002 20:09:49 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFMEPEDHAA.acurtis@onz.com> (raw)
In-Reply-To: <3CF79C16.4B547602@esteem.com>
> Could it be an analog problem? Have you looked at the signals
> comming in on
> a scope?
>
Looking at the signal with a scope is probably a good idea. Here is an
update from today's fun.
1. These is an error in the fcc_enet.c file which causes NO and CRC errors
when running in full-duplex mode. fcc_restart() should be updated to include
FCC_PSMR_LPB when configuring full-duplex mode. (cleared when not)
2. Some relative performance measurements (HHL 2.4.2 vs. 2.4.19pre9)
10T Hub | 100BT switch
-------------------------------------|
2.4.2 | 410KBps | 750KBps |
-------------------------------------|
2.4.19 | 440KBps | 190KBps |
--------------------------------------
RedHat 2.4.18-3 (x86) 3900KBps
3. TOP shows as much as 48% system utilization during a single FTP transfer.
With the fix mentioned in #1, there are 0 errors reported by ifconfig.
I may be missing something but I believe that these numbers are going the
wrong way. There is still the question of performance decrease when using a
100BT switch. Signal intregety can not be the only suspect considering the
performance did increase using an older version of the kernel. (although
nothing like the Workstation performance)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-01 3:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 3:25 Poor 8260 FCC Ethernet performance Jean-Denis Boyer
2002-05-31 3:42 ` Allen Curtis
2002-05-31 15:51 ` Conn Clark
2002-06-01 3:09 ` Allen Curtis [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-10 19:26 Rune Torgersen
2004-06-09 22:33 Rune Torgersen
2004-06-10 17:56 ` Dan Malek
2004-06-09 22:19 Rune Torgersen
2004-06-09 22:27 ` Gary Thomas
2004-06-07 17:33 VanBaren, Gerald (AGRE)
2004-06-08 6:29 ` Wojciech Kromer
2004-06-07 12:32 Dayton, Dean
2004-06-07 12:14 Dayton, Dean
2004-06-07 12:16 ` Pantelis Antoniou
2004-06-06 18:00 Adisorn Ermongkonchai
2004-06-07 12:51 ` Mark Chambers
2004-06-07 17:21 ` Adisorn Ermongkonchai
2002-05-31 3:07 Allen Curtis
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=NCBBIINEHIPFGJPLBEIFMEPEDHAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=clark@esteem.com \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).