From: "David S. Miller" <davem@redhat.com>
To: ak@muc.de
Cc: akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: khttpd rotten?
Date: Fri, 10 May 2002 03:49:22 -0700 (PDT) [thread overview]
Message-ID: <20020510.034922.112319314.davem@redhat.com> (raw)
In-Reply-To: <m3elgk8ftq.fsf@averell.firstfloor.org>
From: Andi Kleen <ak@muc.de>
Date: 10 May 2002 12:20:17 +0200
It is basically impossible without hardware support/major stack changes to
do it securely for networking RX. The problem is that to put data directly
from the NIC into an user space address range the NIC already needs
to demultiplex the sockets before it starts to DMA.
Sun's Cassini gigabit chips have the infrastructure. It's a very
simple onboard header parser (it's not a real CPU, just some thick
ASIC logic). You write small header parsing scripts plus provide it
with a socket cache table, it accumulates data into pages from the
streams for you.
Of course all of this is moot until we can actually write a driver
for one of these cards with such features (I'm working on it for
Cassini and things look good right now).
For userspace you would need to put it into an page aligned buffer and
change the page tables of the user space process, but especially on SMP
that is usually slower than just copying. Managing the stuff in a shared
memory segment is also likely not secure
Alexey already did hacks to make this work on xmit, we have all of the
infrastructure really due to the direct I/O bits.
[There is a special hack in the stack to do it for network sniffing,
but it is not general purpose enough for real protocols]
RX TCP is very doable with the correct hardware. I already have the
implementation in my head given something like Cassini HW.
next prev parent reply other threads:[~2002-05-10 11:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 0:28 Dan Kegel
2002-05-06 2:14 ` David S. Miller
2002-05-06 2:39 ` Dan Kegel
2002-05-06 10:23 ` Christoph Hellwig
2002-05-06 11:28 ` [PATCH] " Dan Kegel
2002-05-06 17:23 ` Luigi Genoni
2002-05-09 9:49 ` David S. Miller
2002-05-09 10:09 ` Christoph Hellwig
2002-05-09 13:04 ` Luigi Genoni
2002-05-11 0:13 ` Ken Brownfield
2002-05-06 14:17 ` Tux in main kernel tree? (was khttpd rotten?) Roy Sigurd Karlsbakk
2002-05-06 16:08 ` Andy Carlson
2002-05-06 23:35 ` Anton Blanchard
2002-05-07 14:42 ` Alan Cox
2002-05-07 15:03 ` Andrea Arcangeli
2002-05-07 15:26 ` Alan Cox
2002-05-07 15:38 ` Andrea Arcangeli
2002-05-07 16:02 ` Luigi Genoni
2002-05-06 17:21 ` Dan Kegel
2002-05-06 18:42 ` John Stoffel
2002-05-06 19:07 ` Diego Calleja
2002-05-06 19:18 ` Cort Dougan
2002-05-06 20:47 ` Michael Rothwell
2002-05-09 11:20 ` Appications in kernelspace (was:Tux in main kernel tree?) Anders Peter Fugmann
2002-05-06 21:52 ` Tux in main kernel tree? (was khttpd rotten?) Paul Jakma
2002-05-09 11:28 ` john slee
2002-05-07 3:00 ` J Sloan
2002-05-09 11:40 ` khttpd rotten? john slee
2002-05-09 11:29 ` David S. Miller
2002-05-09 19:30 ` Andrew Morton
2002-05-09 19:35 ` David S. Miller
2002-05-09 19:39 ` Martin Dalecki
2002-05-10 10:20 ` Andi Kleen
2002-05-10 10:49 ` David S. Miller [this message]
2002-05-09 20:12 ` Ian Molton
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=20020510.034922.112319314.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@muc.de \
--cc=akpm@zip.com.au \
--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®