From: Mel Gorman <mel@csn.ul.ie>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Poor performance with pcnet32 on SMP
Date: Tue, 25 Mar 2003 15:45:39 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.53.0303251538230.22295@skynet> (raw)
In-Reply-To: <3E7B5B41.2070308@us.ibm.com>
On Fri, 21 Mar 2003, Dave Hansen wrote:
> I have no problems copying between two 2.5.65 machines. In fact, my
> speeds are ~10 MBytes/sec. (yes, megabytes)
>
I lied, I didn't give up. This struck a chord with me for some reason. I
have the following
A - 2.5 SMP machine
B - 2.4 UP machine on *same* subnet as A
C - Web server on different subnet, behind firewall but same LAN
I have a 10MB file that I dd'd from /dev/zero on the webserver
wget http://C/~mel/10mb_file
Speed starts at 7kB/s and drops slowly to a crawl. Down with that sort of
thing. I set up a port forwarder (called aproxy) on machine B that
forwards port 80 on B to port 80 on C and try the wget again.
wget http://B/~mel/10mb_file (obviously this forwarding to machine C)
Download starts at 30kB/s and maintains it. A wget from B to C can
download at about 50kB/s but I am assuming that it is related to port
forwarding overhead as much as anything else. I am not sure what this
result means but I thought it was significant. It would seem that as well
as being SMP related, connecting to a different subnet or connecting
through a firewall is also significant.
--
Mel Gorman
MSc Student, University of Limerick
http://www.csn.ul.ie/~mel
next prev parent reply other threads:[~2003-03-25 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 23:54 Mel Gorman
2003-03-21 18:34 ` Dave Hansen
2003-03-25 15:20 ` Mel Gorman
2003-03-25 15:45 ` Mel Gorman [this message]
2003-03-22 6:30 ` Willy Tarreau
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=Pine.LNX.4.53.0303251538230.22295@skynet \
--to=mel@csn.ul.ie \
--cc=haveblue@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®