From: Joseph Garcia <jpgarcia@execpc.com>
To: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Network efficiency issue
Date: Wed, 19 Jan 2000 13:34:36 -0600 [thread overview]
Message-ID: <388611CC.68CE63BC@execpc.com> (raw)
My wallstreet/300 has an issue with FTP transfers. Incoming transfers work fine
at the full 10Mbit potential, however outgoing transfers are extremely slow,
around 75k/s. This holds true of multiple server daemons and client apps. I
have tried this against serveral computers, and it is consistent. All file
transfers in the FTP protocol originating from my book are slow. A switched hub
reported several collisions/sec when i tried using it, and this should not
happen. NFS, etc seem to be unaffected by this issue/bug.
My best guess is that since FTP tends to be fairly raw and with little overhead,
this could be a flow control issue in the kernel. I can supply my kernel
configuration if desired. this occurs with a 2.2.14/Linus and a recent
2.3.39/Paul's Linuxcare rsync.
Any input would be greatly appreacated. Thank you for your time.
--
Joseph P. Garcia jpgarcia@execpc.com jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate Student Employee - Systems Programmer
University of Wisconsin - Madison UW Lidar Group
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-01-19 19:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=388611CC.68CE63BC@execpc.com \
--to=jpgarcia@execpc.com \
--cc=linuxppc-dev@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 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.