From: Robert Love <rml@tech9.net>
To: J Sloan <jjs@lexus.com>
Cc: john slee <indigoid@higherplane.net>, J Sloan <joe@tmsusa.com>,
linux-kernel@vger.kernel.org
Subject: Re: tux officially in kernel?
Date: 14 Feb 2002 18:54:41 -0500 [thread overview]
Message-ID: <1013730883.807.251.camel@phantasy> (raw)
In-Reply-To: <3C6C4942.4050305@lexus.com>
In-Reply-To: <Pine.LNX.4.30.0202111313100.28040-100000@mustard.heime.net> <3C67F327.8010404@tmsusa.com> <20020213135841.GB4826@higherplane.net> <3C6C4942.4050305@lexus.com>
On Thu, 2002-02-14 at 18:33, J Sloan wrote:
> So, just out of curioisity, why is khttpd in
> the kernel? If there were any web server
> in the mainline kernel I'd think it'd be tux -
Personally khttpd should be ripped from the kernel. It is a nice, uh,
example. Or something.
TUX touches enough code that it isn't a clear decision to merge,
although it is certainly worth it. I, however, think we are rapidly
approaching the point, if not there already, that with a zero-copy
network driver userspace can perform as good as TUX with none of the
downsides. That was part of Ingo's goal and a lot of the benefits -
sendfile etc - are a result of TUX.
Anyhow, if I recall correctly, X15 performed better than TUX.
Robert Love
next prev parent reply other threads:[~2002-02-14 23:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 12:49 tux officially in kernel? Roy Sigurd Karlsbakk
2002-02-11 16:36 ` J Sloan
2002-02-13 13:58 ` john slee
2002-02-14 23:33 ` J Sloan
2002-02-14 23:54 ` Robert Love [this message]
2002-02-15 1:00 ` Ken Brownfield
2002-02-15 12:36 ` john slee
2002-02-15 21:11 ` David Lang
2002-02-15 21:35 ` Benny Sjostrand
2002-02-15 23:48 ` Luigi Genoni
2002-02-16 18:59 ` Jason Czerak
2002-02-16 19:25 ` jjs
-- strict thread matches above, loose matches on Subject: below --
2002-02-15 16:37 Dan Kegel
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=1013730883.807.251.camel@phantasy \
--to=rml@tech9.net \
--cc=indigoid@higherplane.net \
--cc=jjs@lexus.com \
--cc=joe@tmsusa.com \
--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