From: "David griego" <dagriego@hotmail.com>
To: jgarzik@pobox.com
Cc: alan@storlinksemi.com, linux-kernel@vger.kernel.org
Subject: Re: Alan Shih: "TCP IP Offloading Interface"
Date: Mon, 14 Jul 2003 13:23:12 -0700 [thread overview]
Message-ID: <Sea2-F51JQjdF8qoH2800011794@hotmail.com> (raw)
>From: Jeff Garzik <jgarzik@pobox.com>
>To: David griego <dagriego@hotmail.com>
>CC: alan@storlinksemi.com, linux-kernel@vger.kernel.org
>Subject: Re: Alan Shih: "TCP IP Offloading Interface"
>Date: Mon, 14 Jul 2003 16:03:01 -0400
>
>David griego wrote:
>>Intel Clusters and Network Storage Volume Platforms Lab reported that it
>>takes about 1MHz to process 1Mbps on a PIII. Using this rule of thumb
>>(they showed it scaling from 400MHz to 800MHz) it would take 10GHz to
>>process 10Mbps. Well you might say "what about multi-processers?" This
>
>Um. It doesn't take nearly 10Ghz to handle 10Mbps, or even 100Mbps.
Err. Make that 10GHz for 10Gbps :-)
>
>
>>would be good for people that have multi-processors, but there is a large
>>segment of embedded processors that are not going have SMP, or be at 10GHz
>>anytime soon. Besides that processing interrupts does not scale across
>>MPs liniarly. The truth is that communication speeds are outpacing
>>processor speeds at this time.
>
>If the host CPU is a bottleneck after large-send and checksums have been
>offloaded, then logically you aren't getting any work done _anyway_. You
>have to interface with the net stack at some point, in which case you incur
>a fixed cost, for socket handling, TCP exception handling, etc.
Still other processing going on like RAID, NFS, or CIFS.
>
>Maybe somebody needs to be looking into AMP (asymmetric multiprocessing),
>too.
Nice artical on AMP for ATM. I'll try to find a pointer.
>
> Jeff
>
>
>
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
next reply other threads:[~2003-07-14 20:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 20:23 David griego [this message]
[not found] <Sea2-F66GGORm1u51rM00012573@hotmail.com>
2003-07-15 11:18 ` Alan Shih: "TCP IP Offloading Interface" Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-07-14 21:51 David griego
2003-07-14 20:29 David griego
2003-07-14 20:19 David griego
2003-07-14 20:31 ` Alan Shih
2003-07-14 20:34 ` Alan Cox
2003-07-14 21:53 ` Deepak Saxena
2003-07-17 22:31 ` Bill Davidsen
2003-07-14 19:43 David griego
2003-07-14 20:03 ` Jeff Garzik
2003-07-14 20:23 ` Alan Cox
2003-07-14 20:05 ` Alan Cox
2003-07-14 20:30 ` Shawn
2003-07-15 5:58 ` Werner Almesberger
2003-07-14 19:14 David griego
2003-07-14 19:26 ` Jeff Garzik
2003-07-15 12:42 ` Jesse Pollard
2003-07-14 19:46 ` Alan Cox
2003-07-14 18:46 David griego
2003-07-14 19:02 ` Jeff Garzik
2003-07-14 21:22 ` Deepak Saxena
2003-07-14 21:45 ` Jeff Garzik
2003-07-15 5:27 ` Werner Almesberger
2003-07-14 19:42 ` Alan Cox
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=Sea2-F51JQjdF8qoH2800011794@hotmail.com \
--to=dagriego@hotmail.com \
--cc=alan@storlinksemi.com \
--cc=jgarzik@pobox.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;
as well as URLs for NNTP newsgroup(s).