Linux-kernel mailing list archive 1999-23,: Re: Announce: kHTTPd 0.1.0

# Re: Announce: kHTTPd 0.1.0

Tigran Aivazian (tigran@sco.COM)
Mon, 7 Jun 1999 10:56:02 +0100 (BST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Alan Cox: "Re: [PROBLEM+PATCH] 2.X zero-length read on non-empty pipe returns EAGAIN"
- Previous message: Aaron T Porter: "Re: mailing list problems?"

Hi,

Just an idea - would it be possible, instead of having to manually insmod
khttp (and keep it loaded all the time which defeats the purpose of it
being a module rather than in the kernel), to modify the networking code
which accepts the connection request and does a
request_module("serve-tcp-port-80") (with alias serve-port-80 khttpd) to
load your khttpd automagicaly?

This could be useful in the future when more inkernel network servers are
written.

Regards,
------
Tigran A. Aivazian | http://www.sco.com
Escalations Research Group | tel: +44-(0)1923-813796
Santa Cruz Operation Ltd | http://www.aivazian.demon.co.uk

On Sat, 5 Jun 1999, Arjan van de Ven wrote:

> Hi,
>
> I have created a kernel-based http-daemon, implemented as a loadable
> module. It started with a discussion on the linux-future list, where two
> groups couldn't agree if kernel-based httpd is a good idea.
>
> I have created such a daemon, so the concept and performance are
> (somewhat) known. Even if the result at the end is that kHTTPd is _not_ a
> good idea (I think it is, though), it can be used for pinpointing
> performance-bottlenecks in the network-code. (kHTTPd can easily saturate a
> 100 Mbit network with a 350 Mhz K6-2 server).
>
> kHTTPd is GPL'd and can be found at
>
> http://www.fenrus.demon.nl
>
> Greetings,
> Arjan van de Ven
>
>
>
> ----- Portion of the README -----
>
> 1. Concept
>
> kHTTPd is a http-daemon (webserver) for Linux. kHTTPd is different
> from other webservers in that it runs from within the Linux-kernel
> as a module (device-driver).
>
> kHTTPd handles only static (file based) web-pages, but it is able
> to use a "regular" webserver (Apache and others) to do all the
> non-static content.
>
> Static web-pages are, in general, not a very complex thing to do,
> but these are very important nevertheless, since virtually all
> images are static, and a large portion of the html-pages are
> static also. A "regular" webserver has little added value for
> static pages, it is simply "copy file to network". The Linux kernel
> is very good at that, for example the nfs (network file system)
> daemon also runs in the kernel.
>
>
>
>
> -
> Linux-future: thinking about the future of the Linux kernel
> Archive: http://humbolt.nl.linux.org/lists/
> Wish list: http://users.ox.ac.uk/~mert0236/linux-future.html
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: Alan Cox: "Re: [PROBLEM+PATCH] 2.X zero-length read on non-empty pipe returns EAGAIN"
- Previous message: Aaron T Porter: "Re: mailing list problems?"