[lkml]   [2000]   [Oct]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: kqueue microbenchmark resul

>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?


... recursive make suxx!

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:45    [W:0.035 / U:0.864 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site