From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: "Xiaoliang \(David\) Wei" <weixl@caltech.edu>
Cc: netdev@oss.sgi.com
Subject: Re: Poor gige performance with 2.4.20-pre*
Date: Sun, 29 Sep 2002 00:34:02 -0600 [thread overview]
Message-ID: <200209290634.g8T6Y2o08439@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <002f01c2675d$b642b640$f5f2010a@weixl>
Xiaoliang Wei writes:
> 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)?
This is all on a LAN (of course; expecting good performance from a WAN
is pretty futile). I use a buffer size of 256 KiB.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2002-09-29 6:34 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
2002-09-29 6:34 ` Richard Gooch [this message]
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=200209290634.g8T6Y2o08439@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=netdev@oss.sgi.com \
--cc=weixl@caltech.edu \
/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).