> Which gives rise to the question why use khttp at all. The point was to
> avoid user mode completely.
>
I am not a kernel or http server expert. But is there really a reason
that a kernel based implementation would be inherently faster than the
same thing written for user space? Here I am talking about a
specialized server, optimized to the hilt for serving static pages to a
large number of clients, with decisions about how to handle threading,
etc. made for maximum performance from the ground up, and with the
ability to hand off more complicated stuff to another "full" web
server. On the other hand, as a module, having the *option* to use
khttpd wouldn't hurt.
-Steve
-
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/