From: "Xiaoliang \(David\) Wei" <weixl@caltech.edu>
To: "Richard Gooch" <rgooch@ras.ucalgary.ca>, <netdev@oss.sgi.com>
Subject: Re: Poor gige performance with 2.4.20-pre*
Date: Sat, 28 Sep 2002 19:12:50 -0700 [thread overview]
Message-ID: <002f01c2675d$b642b640$f5f2010a@weixl> (raw)
In-Reply-To: 200209282257.g8SMvta32527@vindaloo.ras.ucalgary.ca
Hi,
Did you do the experiments on WAN or LAN? What's the other
configurations, such as: The sending/receiving buffer(I think it should be
larger than Bandwidth*Delay)?
> Hi, all. For a while now I've noticed poor performance with gige
> cards under 2.4.19 and 2.4.20-pre*. At first I thought it was because
> of the cheap-ass Addtron cards I bought (these use the ns83820 chip).
> But now that the Intel E1000 cards are pretty cheap too, I've grabbed
> a couple (part number: PWLA8390MT) and see the same problem. In fact,
> the E1000 cards are no better than the Addtron cards. I'm using the
> D-Link DGS-1008T 8-port gige switch. MTU=1500 bytes.
>
> The basic test I do is to send 100 MB over a TCP connection from one
> machine to the other. The results are:
>
> Dual PIII 450 MHz -> Dual Athalon 1.6 GHz yields 58 MB/s
> Dual Athalon 1.6 GHz -> Dual PIII 450 MHz yields 23 MB/s
>
> This is quite a bit less than what gige is supposed to give. Is this
> expected?
>
> Regards,
>
> Richard....
> Permanent: rgooch@atnf.csiro.au
> Current: rgooch@ras.ucalgary.ca
>
>
>
>
next prev parent reply other threads:[~2002-09-29 2:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 22:57 Poor gige performance with 2.4.20-pre* Richard Gooch
2002-09-29 2:12 ` Xiaoliang (David) Wei [this message]
2002-09-29 6:34 ` Richard Gooch
2002-09-30 0:45 ` Benjamin LaHaise
2002-09-30 0:53 ` Richard Gooch
2002-09-29 2:32 ` Ben Greear
2002-09-29 19:22 ` Richard Gooch
2002-09-29 19:32 ` Ben Greear
2002-09-29 20:54 ` Richard Gooch
2002-09-30 21:21 ` Jon Fraser
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='002f01c2675d$b642b640$f5f2010a@weixl' \
--to=weixl@caltech.edu \
--cc=netdev@oss.sgi.com \
--cc=rgooch@ras.ucalgary.ca \
/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.