Jamie Lokier <lk@tantalophile.demon.co.uk> writes:
> For this sort of thing, I would like to see an option to automatically
> set the non-blocking flag on accept(). To really squeeze the system
> calls, you could also automatically epoll-register on accept(), and
> for super bonus automatically do the accept() at event delivery time.
> But it's getting very silly at that point.
> -- Jamie
I would like to see a new kind of nonblocking flag that implies the
use of epoll. So instead of giving O_NONBLOCK to fctnl(F_SETFL), you
give O_NONBLOCK_EPOLL. In addition to becoming non-blocking, the
socket is added to epoll interest set. Furthermore, if the socket is
a "listener" socket, all connections accepted on the socket inherit
the non-blocking status and are added automatically to the same epoll
interest set. It's true that this can get silly though. I'd like to
do the same with other flags, like TCP_CORK.
-- Buck
> --
> To unsubscribe, send a message with 'unsubscribe linux-aio' in
> the body to majordomo@kvack.org. For more info on Linux AIO,
> see: http://www.kvack.org/aio/
-
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/
This archive was generated by hypermail 2b29 : Thu Nov 07 2002 - 22:00:21 EST