> I dont see why Tux should be merged. If we have people achieving the same
> performance in user space with the core facilities tux added to the kernel
> like the better irq/sendfile stuff why bother merging tux ?
1. We have khttpd, which should be replaced by something faster.
2. Tux makes a nice example.
3. Tux can be the fastest. If it isn't, it needs more work.
Toward the end of the X15 discussion, Ingo Molnar mentioned
something he'd not implemented yet. I don't recall exactly,
but for sure Tux hasn't run out of optimizations to do.
Also the kernel-CGI feature has not been used in benchmarks.
Tux has been running user code.
IMHO the Tux server could be renamed "khttpd" and dropped in
with whatever is needed to be compatible for existing setups.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/