John Gardiner Myers wrote:
> Nonetheless, the requirement for user space to test the condition after
> the registration, not before, is subtle. A program which does these in
> the wrong order is still likely to pass QA and will fail in production
> in a way that will be difficult to diagnose. There is no rational
> reason for the kernel to not test the condition upon registration.
As long as we agree that the kernel may provide spurious readiness
notifications on occasion, I agree. Then /dev/epoll can easily fulfill
this by signaling readiness on everything at registration; more
accurate notifications could be added later as an optimization.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:00:30 EST