From: bert hubert <ahu@ds9a.nl>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org, khttpd mailing list <khttpd-users@zgp.org>
Subject: Re: khttpd vs tux
Date: Sat, 3 Nov 2001 17:49:45 +0100 [thread overview]
Message-ID: <20011103174945.A16538@outpost.ds9a.nl> (raw)
In-Reply-To: <20011103172803.A16411@outpost.ds9a.nl> <Pine.LNX.4.30.0111031744280.8812-100000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0111031744280.8812-100000@mustard.heime.net>; from roy@karlsbakk.net on Sat, Nov 03, 2001 at 05:45:29PM +0100
On Sat, Nov 03, 2001 at 05:45:29PM +0100, Roy Sigurd Karlsbakk wrote:
> > tux holds all records, khttpd has been measured to be slower than some
> > userspace webservers.
>
> What's bad about tux, then? There usually is something...
The main hurdle for Tux is that it is not in the mainstream kernel, and
consists of a patch. I think RedHat has precompiled kernels with Tux in
them. The aa kernels also contain tux.
There are also strong indications that 'zero copy tcp/ip' may enable
userspace webservers to achieve comparable bandwidths (many gbits/second).
See for example X15: http://www.chromium.com/x15tech.html
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
next prev parent reply other threads:[~2001-11-03 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-03 16:21 Roy Sigurd Karlsbakk
2001-11-03 16:28 ` bert hubert
2001-11-03 16:45 ` Roy Sigurd Karlsbakk
2001-11-03 16:49 ` bert hubert [this message]
2001-11-04 5:26 ` [khttpd-users] " Chul Lee
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=20011103174945.A16538@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=khttpd-users@zgp.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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®