mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: More performance for the TCP stack by using additional hardware chip on NIC
Date: Sun, 17 Apr 2005 19:37:18 -0400	[thread overview]
Message-ID: <200504172337.j3HNbJsA004220@laptop11.inf.utfsm.cl> (raw)
In-Reply-To: Message from Andreas Hartmann <andihartmann@01019freenet.de>  of "Sun, 17 Apr 2005 10:17:49 +0200." <d3t63d$3qe$1@pD9F86D3F.dip0.t-ipconnect.de>

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.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

  parent reply	other threads:[~2005-04-18  1:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-17  8:17 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 [this message]
2005-04-18  4:08   ` Kyle Moffett
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=200504172337.j3HNbJsA004220@laptop11.inf.utfsm.cl \
    --to=vonbrand@inf.utfsm.cl \
    --cc=andihartmann@01019freenet.de \
    --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

all inboxes | Powered by JetHome®