> > Cache
> > -----
> > The point was made by an Apache developer that kHTTPd would do a better
> > job if it was just caching requests and that userspace "commands" kHTTPd
> > to send a certain file.
>
> This is the model I like
>
> > If this is true, Alan Cox is right and kHTTPd shouldn't be in the kernel,
> > but the problem with the kernel should be fixed.
> >
> > I don't think this is true though:
> > 1) There already is a cache in the kernel, the buffercache. Caching things
> > twice is insane
>
> So don't cache the data twice, use the page cache. The page cache wants to
> be you friend. I'd agree caching twice is stupid.
>
> Basically instead of khttpd getting requests khttpd sits waiting to be told
> "here is a socket, here is a file, do your stuff then kick me."
Why not asking the kernel to compile file, to copy file, to tar files, or
to do any kind of work. Then we can just get rid of what has been called
useland, in the past, and directly deal with user interface from the
kernel. At this step, there is no reason to distinguish the kernel from
anything else, so we can get rid of the word "kernel" with regards to
system architecture and a generic word as "crapware" will be enough to
identify the result without any ambiguity.
(Just sci-fi, I hope will never happen, but who knows ...)
Gérard.
-
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/