> Now, next time around the loop, we get a notification for an event > when there is no data to read. The application now must be prepared > to handle this case (meaning no blocking read() calls can be used). > -- > Jonathan If the programmer never wants to block in a read call, he should never do a blocking read anyway. There's no standard that requires readability at time X to imply readability at time X+1. DS - 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/
- Re: kqueue microbenchmark results Jonathan Lemon
- Re: kqueue microbenchmark results Simon Kirby
- Re: kqueue microbenchmark results Jamie Lokier
- Re: kqueue microbenchmark results Simon Kirby
- Efficient edge-triggered event interface Jamie Lokier
- Re: kqueue microbenchmark results Jonathan Lemon
- Re: kqueue microbenchmark results Simon Kirby
- Re: kqueue microbenchmark results Jamie Lokier
- Re: kqueue microbenchmark results Jonathan Lemon
- Re: kqueue microbenchmark results Jonathan Lemon
- Re: kqueue microbenchmark results David Schwartz
- Re: kqueue microbenchmark resul... Jonathan Lemon
- RE: kqueue microbenchmark resul... David Schwartz
- Re: kqueue microbenchmark resul... Alfred Perlstein
- Re: kqueue microbenchmark resul... Terry Lambert
- Re: kqueue microbenchmark resul... Terry Lambert
- RE: kqueue microbenchmark resul... David Schwartz
- Re: kqueue microbenchmark resul... Jamie Lokier
- Re: kqueue microbenchmark resul... Alfred Perlstein
- Re: kqueue microbenchmark results Gideon Glass
- Re: kqueue microbenchmark resul... Jonathan Lemon