Possibly lost socket accept notifications? about mio HOT 4 CLOSED

@zslayton It seems that you have to put the accept in a loop.

I forked your gist in https://gist.github.com/ayosec/f4bf228b6e7826889156#file-gistfile1-rs-L38-L43

The important snippet:

loop {
  match self.server.acceptor.accept() {
    Ok(client) => {
      if client.would_block() {
        break
      } else {
      // ...

from mio.

That did it, thanks! Not only did it get to the full 10,000 it got there in a fraction of the time it used to. Can you explain how the looping is helping here?

from mio.

MIO sets epoll into edge triggered mode (see here),

Basically the OS will notify you once for ALL pending events. Once the notification is sent for a socket, you have to read in a loop to make sure that you consume all of them (aka, do it in a loop) to make sure that you get all the events that that are pending.

Hope this makes sense.

from mio.

Thanks for explaining!

On Mon, Nov 10, 2014 at 6:57 PM, Carl Lerche [email protected]
wrote:

MIO sets epoll into edge triggered mode (see here
http://man7.org/linux/man-pages/man7/epoll.7.html),

Basically the OS will notify you once for ALL pending events. Once the
notification is sent for a socket, you have to read in a loop to make sure
that you consume all of them (aka, do it in a loop) to make sure that you
get all the events that that are pending.

Hope this makes sense.

—
Reply to this email directly or view it on GitHub
#44 (comment).

from mio.