From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: LinuxPPC Embedded Mailing List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: TCP/IP performance on the 855T/860T
Date: Thu, 29 Jun 2000 22:35:05 -0400 [thread overview]
Message-ID: <395C0759.9C8A6C83@netx4.com> (raw)
In-Reply-To: 20000630013309.7F172BB@elph.research.canon.com.au
Graham Stoney wrote:
> So has anyone had a chance to look at where exactly in the TCP/IP stack the
> bottleneck is since this was last discussed?
Yes, you can do a few things with TCP/IP windows to help a little,
but it is only a few percent.
> .... Surely a 50 MHz part with an
> on-chip 100 Mbps Ethernet controller has enough grunt to keep up with a single
> TCP/IP connection.
There isn't any other processor that will do it at that speed.
Dig out an old 486 and try the local loopback test......You wouldn't
be surprised if it can't keep up.
> Any suggestions?
...8260....
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-06-30 2:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-29 12:09 FEC performance on the 855T/860T Graham Stoney
2000-06-29 18:12 ` Dan Malek
2000-06-30 1:33 ` TCP/IP " Graham Stoney
2000-06-30 2:35 ` Dan Malek [this message]
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=395C0759.9C8A6C83@netx4.com \
--to=dan@netx4.com \
--cc=greyham@research.canon.com.au \
--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).