From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: David griego <dagriego@hotmail.com>,
alan@storlinksemi.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Alan Shih: "TCP IP Offloading Interface"
Date: 14 Jul 2003 21:23:09 +0100 [thread overview]
Message-ID: <1058214188.606.139.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3F130C75.3010603@pobox.com>
On Llu, 2003-07-14 at 21:03, Jeff Garzik wrote:
> 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.
>
> Maybe somebody needs to be looking into AMP (asymmetric
> multiprocessing), too.
There isnt currently any evidence it buy you anything, although HT may
change that equation a bit. Its still the same RAM bandwidth and you've
not really gotten rid of most of the socket handling/event/wakeup
overhead either.
next prev parent 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 19:43 Alan Shih: "TCP IP Offloading Interface" David griego
2003-07-14 20:03 ` Jeff Garzik
2003-07-14 20:23 ` Alan Cox [this message]
2003-07-14 20:05 ` Alan Cox
2003-07-14 20:30 ` Shawn
2003-07-15 5:58 ` Werner Almesberger
[not found] <Sea2-F66GGORm1u51rM00012573@hotmail.com>
2003-07-15 11:18 ` 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:23 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: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=1058214188.606.139.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@storlinksemi.com \
--cc=dagriego@hotmail.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).