From: Kyle Moffett <mrmacman_g4@mac.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Andreas Hartmann <andihartmann@01019freenet.de>,
linux-kernel@vger.kernel.org
Subject: Re: More performance for the TCP stack by using additional hardware chip on NIC
Date: Mon, 18 Apr 2005 00:08:41 -0400 [thread overview]
Message-ID: <edb06d05e65c7c2ce2ba008cc673aa29@mac.com> (raw)
In-Reply-To: <200504172337.j3HNbJsA004220@laptop11.inf.utfsm.cl>
On Apr 17, 2005, at 19:37, Horst von Brand wrote:
> Andreas Hartmann <andihartmann@01019freenet.de> said:
>> Alacritech developed a new chip for NIC's
>> (http://www.alacritech.com/html/tech_review.html), which makes it
>> possible
>> to take away the TCP stack from the host CPU. Therefore, the host CPU
>> has
>> more performance for the applications according Alacritech.
>>
>> This sounds interesting.
>
> This idea has been discussed around here a couple of times, and the
> consensus is that it is a bad idea: IP (and upper protocol) processing
> is not expensive, if done right, so this really doesn't buy much; this
> forces a particular interface to networking into the kernel, loosing
> flexibility that way is always bad; there is no access to futzing
> around in between (for example, for firewalling and such); and if the
> "hardware implementation" has bugs, you are screwed.
What I think would be _much_ more useful is a generic low-power
multi-proc
MIPS/PPC system on a PCI card with a certain amount of RAM, etc that
could
be programmed at runtime by the master CPU. Then you lose none of the
flexibility, it can be run in the same endian-mode as the host CPU, and
it
would allow you to program it for much more complicated DMA. You could
do
anything from linux software RAID, audio processing, encryption, TCP/IP
stack acceleration, extra scatter-gather for your disk controller, etc.
If it was low-cost, IE: cheaper than adding extra full-speed CPUs to the
system, and using a decent bi-endian, vector-capable CPU (Like PPC), you
might find that people will buy them for the flexibility. Such a thing
might also be useful for the prezero folks, it could be used (when not
otherwise occupied) for zeroing unused pages.
Personally, I think I'd buy one or two just to tinker with them :-D.
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r
!y?(-)
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2005-04-18 4:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 8:17 More performance for the TCP stack by using additional hardware chip on NIC Andreas Hartmann
2005-04-17 9:07 ` Arjan van de Ven
2005-04-17 10:29 ` Avi Kivity
2005-04-17 10:57 ` Arjan van de Ven
2005-04-17 12:32 ` Avi Kivity
2005-04-17 11:30 ` Willy Tarreau
2005-04-17 12:15 ` Avi Kivity
2005-04-17 19:43 ` Bernd Eckenfels
2005-04-17 20:36 ` David S. Miller
2005-04-18 5:35 ` Avi Kivity
2005-04-17 23:37 ` Horst von Brand
2005-04-18 4:08 ` Kyle Moffett [this message]
2005-04-18 4:28 ` Willy Tarreau
[not found] <3Udkm-7rV-7@gated-at.bofh.it>
[not found] ` <3Ue6L-867-19@gated-at.bofh.it>
[not found] ` <3Ufm9-IB-3@gated-at.bofh.it>
[not found] ` <3Ugid-1w6-25@gated-at.bofh.it>
2005-04-17 19:04 ` Andreas Hartmann
2005-04-18 8:27 ` Denis Vlasenko
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=edb06d05e65c7c2ce2ba008cc673aa29@mac.com \
--to=mrmacman_g4@mac.com \
--cc=andihartmann@01019freenet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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.