From: Zach Brown <zab@zabbo.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Fabio Riccardi <fabio@chromium.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Christopher Smith <x@xman.org>,
Andrew Morton <andrewm@uow.edu.au>,
"Timothy D. Witham" <wookie@osdlab.org>,
David_J_Morse@Dell.com
Subject: Re: X15 alpha release: as fast as TUX but in user space
Date: Wed, 2 May 2001 10:12:00 -0400 [thread overview]
Message-ID: <20010502101200.E28288@erasmus.off.net> (raw)
In-Reply-To: <3AEC8562.887CFA72@chromium.com> <Pine.LNX.4.33.0105021047040.3642-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0105021047040.3642-100000@localhost.localdomain>; from mingo@elte.hu on Wed, May 02, 2001 at 10:50:38AM +0200
> i think Zach's phhttpd is an important milestone as well, it's the first
> userspace webserver that shows how to use event-based, sigio-based async
> networking IO and sendfile() under Linux. (I believe it had some
*blush*
> performance problems related to sigio queue overflow, these issues might
> be solved in the latest kernels.) The zerocopy enhancements should help
> phhttpd as well.
oh, it has a bunch of problems :) over-threading created complexity in
the fast path. It always spends memory on a contiguous header region for
each connection, which may not be valid in the days of zero copy sendmsg.
It does IO in the fast path. And looking back at it, I'm struck by how
naive most of the code is :) :)
I've always been tempted to go back and take a real swing at a
nice content server, but there's only so many hours in the day, and
apache+thttpd+tux complete the problem space. If X15 isn't released
with an open license, I may be tempted yet again :)
- z
next prev parent reply other threads:[~2001-05-02 14:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 7:32 X15 alpha release: as fast as TUX but in user space Ingo Molnar
2001-04-29 21:19 ` Fabio Riccardi
2001-05-01 8:53 ` Ingo Molnar
2001-05-01 17:10 ` Fabio Riccardi
2001-05-01 17:12 ` Ingo Molnar
2001-05-04 1:58 ` Fabio Riccardi
2001-05-04 8:24 ` X15 alpha release Ingo Molnar
2001-05-04 18:07 ` Fabio Riccardi
2001-05-04 8:49 ` X15 alpha release: as fast as TUX but in user space Ingo Molnar
2001-05-04 18:10 ` Fabio Riccardi
2001-05-04 18:38 ` Davide Libenzi
2001-05-09 22:42 ` Fabio Riccardi
2001-05-02 8:50 ` Ingo Molnar
2001-05-02 14:12 ` Zach Brown [this message]
2001-05-03 2:41 ` Fabio Riccardi
2001-05-02 23:19 ` Lincoln Dale
2001-05-03 2:29 ` Linux syscall speed -- was X15 rootin-tootin webserver Michael Rothwell
-- strict thread matches above, loose matches on Subject: below --
2001-04-28 0:18 X15 alpha release: as fast as TUX but in user space Fabio Riccardi
2001-04-28 0:41 ` Aaron Lehmann
2001-04-28 0:49 ` David S. Miller
2001-04-28 1:11 ` Fabio Riccardi
2001-04-28 8:42 ` Ingo Molnar
2001-04-28 13:15 ` Ville Herva
2001-04-28 13:21 ` Ingo Molnar
2001-04-28 13:24 ` Ingo Molnar
2001-04-28 13:30 ` Ville Herva
2001-04-28 13:55 ` Andi Kleen
2001-04-29 21:25 ` Fabio Riccardi
2001-04-30 5:43 ` dean gaudet
2001-04-30 6:39 ` David S. Miller
2001-04-30 19:36 ` Fabio Riccardi
2001-04-30 21:47 ` dean gaudet
2001-04-30 21:52 ` David S. Miller
2001-05-01 7:31 ` Ingo Molnar
2001-05-01 7:25 ` Ingo Molnar
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=20010502101200.E28288@erasmus.off.net \
--to=zab@zabbo.net \
--cc=David_J_Morse@Dell.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--cc=fabio@chromium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=wookie@osdlab.org \
--cc=x@xman.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