From: Reto Baettig <baettig@scs.ch>
To: alexander.eichhorn@rz.tu-ilmenau.de
Cc: root@chaos.analogic.com, linux-kernel@vger.kernel.org
Subject: Re: [Question] Explanation of zero-copy networking
Date: Wed, 09 May 2001 11:56:33 +0200 [thread overview]
Message-ID: <3AF91451.1B989742@scs.ch> (raw)
In-Reply-To: <Pine.LNX.3.95.1010507145625.6441A-100000@chaos.analogic.com> <3AF82D3E.C916B055@rz.tu-ilmenau.de>
> considered to be in the "window of scarcity" (today we have 100MBit
> Ethernets and 133++MB/s PCI). Tomorrow our operating system concepts
> have to cope with 1, 10, ?? Gigabit Ethernets, Infiniband ,
> ... who knows.
We had to write our own RPC mechanism because with the standard-stacks
we had no chance of achieving our goals. We would have loved to use
tcp/ip but it was not possible with Linux 2.2.
Today we achieve almost 200MB/s over our RPC stack and this with the
CPU's almost idle. With TCP/IP and Gig-E we only came up to 60-70MB/s
and then the system was completely busy and unresponsive (Linux 2.4 is
supposed to be better but I doubt that we get a CPU load this low
without zerocopy networking).
We would like to look at the zerocopy ideas of Linux 2.4 and try to
implement our RPC mechanism over zerocopy-TCP (if something like this
exists). We just started with this idea and don't know exactly where to
start yet (we are looking for something like a de-facto zerocopy
standard for sockets)... Any ideas are welcome.
Reto
next prev parent reply other threads:[~2001-05-09 9:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 13:43 [Question] Explanation of zero-copy networking Alexander Eichhorn
2001-05-07 13:56 ` Alan Cox
2001-05-07 16:12 ` Richard B. Johnson
2001-05-07 17:53 ` Francois Romieu
2001-05-07 18:00 ` Blue Lang
2001-05-07 18:25 ` dean gaudet
2001-05-07 19:54 ` Richard B. Johnson
2001-05-07 20:23 ` dean gaudet
2001-05-08 11:09 ` Bjorn Wesen
2001-05-08 17:30 ` Alexander Eichhorn
2001-05-09 9:56 ` Reto Baettig [this message]
2001-05-07 18:30 ` Pekka Pietikainen
2001-05-07 19:00 ` Venkatesh Ramamurthy
2001-05-08 7:18 ` Jamie Lokier
2001-05-09 15:13 ` Eric W. Biederman
2001-05-07 18:21 ` dean gaudet
2001-05-07 21:59 ` Alan Cox
2001-05-08 16:20 ` Jamie Lokier
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=3AF91451.1B989742@scs.ch \
--to=baettig@scs.ch \
--cc=alexander.eichhorn@rz.tu-ilmenau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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.