Though for the kinds of things I'm doing, we use threads a lot in a
single main process anyway. There are context switches (though we're
investigating keeping moving that mostly to the user-space thread
library).
The kernel context switching issue is still relevant because (a) other
control processes, general handy daemons and the like and the odd shell
are still running occasionally; (b) I'm personally not convinced that
polling DMA'd system memory throughout the user-space code (U-Net style)
is much better than using hardware interrupts, and it certainly
complicates the application, so I'd like to see the kernel do a good job
itself.
-- Jamie
-
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/