A way to add EPOLLPRI event type to the epoll selector about mio HOT 7 CLOSED

EPOLLPRI is enable by default when using readable interest.

from mio.

EPOLLPRI is enable by default when using readable interest.

Really? I don't see this backed by the code and I do not get any EPOLLPRI events from the kernel.
Have a look here:

I made a "horrible hack" here: poeschel@538970c
With this change I do receive the EPOLLPRI events.

from mio.

EPOLLPRI is an output flags only if I recall correctly, so you should see it when use register readable interest. If you want to test this for yourself you can send some Out-Of-Bound (MSG_OOB) data to a TcpStream and you should see an event with EPOLLPRI.

from mio.

Hello, I am working with @poeschel on this problem. We have created a small test project which can be found here: https://github.com/poeschel/mio-pollpri-test

The program sends messages over a TCP socket and checks the received events. We also send a MSG_OOB message. There you can see that the MSG_OOB is in fact received, but does not contain the EPOLLPRI flag, and does not have the priority set to true. Output from the program (only the second message to keep it brief) in this case:

[src/main.rs:43] event = Event {
    token: Token(
        1,
    ),
    readable: true,
    writable: false,
    error: false,
    read_closed: false,
    write_closed: false,
    priority: false,           <<<<<
    aio: false,
    lio: false,
    details: epoll_event {
        events: EPOLLIN,       <<<<<
        u64: 1,
    },
}

With the "horrible hack" posted above, the output changes to:

[src/main.rs:43] event = Event {
    token: Token(
        1,
    ),
    readable: true,
    writable: false,
    error: false,
    read_closed: false,
    write_closed: false,
    priority: true,                   <<<<<
    aio: false,
    lio: false,
    details: epoll_event {
        events: EPOLLIN|EPOLLPRI,     <<<<<
        u64: 1,
    },
}

You can see that the flags contains EPOLLPRI and the priority field is set to true. That likely means MSG_OOB was received only because it also contains the EPOLLIN flag.

As mentioned above, we work with V4L2, and our events do only contain EPOLLPRI. Changing the selector to generally also accept EPOLLPRI events like in our hack, seems like a big breaking change, so we are not quite sure how to proceed.

from mio.

Hello, I am working with @poeschel on this problem. We have created a small test project which can be found here: https://github.com/poeschel/mio-pollpri-test

This program is incorrect. You should get only a single event for the send on line 20. You should drain the readiness, see https://docs.rs/mio/latest/mio/struct.Poll.html#readiness-operations, to get another event.

from mio.

I created pull-request #1646 that demonstrates the issue a bit better.

from mio.

... and I would suggest something like this as a possible solution: poeschel@282edd3

from mio.