I agree... but we might eventually have events that apps aren't
interested in. No harm in letting app specify an interest mask once.
> Taking the idea further, I would prefer that ALL non-blocking sockets
> are automatically added to the epoll interest set if the application
> has already called epoll_create().
That would prevent apps from having more than one i/o readiness
notification event source. This is a problem for modular
software, where you try to combine libraries in a multithreaded
program.
- Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/