>The effect of M:N on UP systems should be even more clear. Your
>multithreaded apps can't profit of parallelism but they do not
>add load to the system scheduler. The drawback: more syscalls
>(I think about removing the need for
>flags=fcntl(GETFLAGS);fcntl(fd,NONBLOCK);write(fd);fcntl(fd,flags))
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 why select-loop and poll-loop type
servers are bursty.
DS
-
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/
This archive was generated by hypermail 2b29 : Mon Sep 30 2002 - 22:00:20 EST