> The main reason I write multithreaded apps for single CPU systems is to
> protect against ambush. Consider, for example, a web server. Someone sends it
> an obscure request that triggers some code that's never run before and has to
> fault in. If my application were single-threaded, no work could be done until
> that page faulted in from disk.
This is interesting--I hadn't considered this as most of my work for the
past while has been on embedded systems with everything pinned in ram.
Have you benchmarked this? I was under the impression that the very
fastest webservers were still single-threaded using non-blocking io.
Chris
-
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/