All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
	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 06:28:07 +0200	[thread overview]
Message-ID: <20050418042807.GC777@alpha.home.local> (raw)
In-Reply-To: <edb06d05e65c7c2ce2ba008cc673aa29@mac.com>

On Mon, Apr 18, 2005 at 12:08:41AM -0400, Kyle Moffett wrote:
(...) 
> 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.

it would be really interesting, it would be sort of an I/O coprocessor,
but unfortunately, it would half the PCI bandwidth (which is already a
problem with 10 Gbps) be cause the data would have to go from the NIC
to the copro then from the copro to system RAM.

Or if this copro contains large amounts of RAM, then the applications
can manipulate data directly on the card (and the copro could provide
remote memcpy, memmove, etc...), thus eliminating copies. But in this
case, it would require many modifications on both the kernel and the
application.

> 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.

Then you should take a look at some hardware RAID controllers or even
some special intel NICs, both of which often come with an i960 or PPC
onboard. It might become a good start, and if you can show someting
interesting, we already know there's one guy here who can build the
full-speed CPU from the specs :-)

Cheers,
Willy


  reply	other threads:[~2005-04-18  4:28 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
2005-04-18  4:28     ` Willy Tarreau [this message]
     [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=20050418042807.GC777@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=andihartmann@01019freenet.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --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.