Logan Gunthorpe <logang@xxxxxxxxxxxx> writes:
> On 2020-03-13 11:46 a.m., Sebastian Andrzej Siewior wrote:
>> 1) It cannot work with EPOLLEXCLUSIVE
>
> Why? You don't explain this.
man epoll_ctt(2)
EPOLLEXCLUSIVE (since Linux 4.5)
Sets an exclusive wakeup mode for the epoll file descriptor that is
being attached to the target file descriptor, fd. When a wakeup event
occurs and multiple epoll file descriptors are attached to the same
target file using EPOLLEXCLUSIVE, one or more of the epoll file
descriptors will receive an event with epoll_wait(2).
As this uses complete_all() there is no distinction possible, because
complete_all() wakes up everything.
> And I don't see how this patch would change anything to do with the
> call to poll_wait(). All you've done is open-code the completion.
wake_up_interruptible(x) resolves to:
__wake_up(x, TASK_INTERRUPTIBLE, 1, NULL)
which wakes exactly 1 exclusive waiter.
Also the other way round is just working because the waker side uses
complete_all(). Why? Because completion internally defaults to exclusive
mode and complete() wakes exactly one exlusive waiter.
There is a conceptual difference and while it works for that particular
purpose to some extent it's not suitable as a general wait notification
construct.
Thanks,
tglx
