kqueue microbenchmark resul
Quoted 4 lines
In fact, if you did leave the read queued in a daemon using
select()before, you'd keep looping endlessly taking all CPU and never idle because there would always be read data available.
Also, level triggered notifications would also seem to cause multiple thread wakeups and thundering herd problems when there are multiple worker threads reading from the same queue.
How does (?) kevent avoid this from happening?
Mark
--
... recursive make suxx!
------------------------------------------------------------------------
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/