From: Dave Jones <davej@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
Ingo Molnar <mingo@elte.hu>, Ted Merrill <atheros@embuildsw.com>
Subject: Re: khttpd fate
Date: Tue, 21 Jul 2009 21:57:07 -0400 [thread overview]
Message-ID: <20090722015706.GB6025@redhat.com> (raw)
In-Reply-To: <4A665F09.7050104@zytor.com>
On Tue, Jul 21, 2009 at 05:36:25PM -0700, H. Peter Anvin wrote:
> On 07/21/2009 05:20 PM, Kyle McMartin wrote:
> >
> > I think it kind of got replaced by tux, which Red Hat shipped for a
> > while, but has been dropped now. I seem to recall davej mentioning a
> > while ago that apache had gotten much better at serving static content,
> > which is what khttpd/tux were very good at.
> >
>
> Also, lighttpd does really well, all in userspace. After all, static
> http serving really is mostly a bit of header parsing followed by
> sendfile(), so as long as a user-space process doesn't just sit on a
> bunch of memory it can be done very cheaply.
I think the rise of dynamically generated content was a big thing that
killed it off. With more and more of the web getting ajaxified, and the
php etc being offloaded to apache anyway, it just makes more sense to
have one webserver do everything as long as it's "fast enough".
I wrote something up on this a few years back when I made the decision to
drop Tux from the Fedora kernel. http://kernelslacker.livejournal.com/tag/tux
Dave
next prev parent reply other threads:[~2009-07-22 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 1:15 khttpd fate Luis R. Rodriguez
2009-07-22 0:20 ` Kyle McMartin
2009-07-22 0:36 ` H. Peter Anvin
2009-07-22 1:57 ` Dave Jones [this message]
2009-07-22 4:47 ` H. Peter Anvin
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=20090722015706.GB6025@redhat.com \
--to=davej@redhat.com \
--cc=arjan@infradead.org \
--cc=atheros@embuildsw.com \
--cc=hpa@zytor.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=mingo@elte.hu \
/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