Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 1 Nov 2002 15:08:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 1 Nov 2002 15:08:01 -0500 Received: from bjl1.asuk.net.64.29.81.in-addr.arpa ([81.29.64.88]:24502 "EHLO bjl1.asuk.net") by vger.kernel.org with ESMTP id ; Fri, 1 Nov 2002 15:08:00 -0500 Date: Fri, 1 Nov 2002 20:14:14 +0000 From: Jamie Lokier To: Charlie Krasic Cc: Dan Kegel , Davide Libenzi , Linux Kernel Mailing List , linux-aio@kvack.org, lse-tech@lists.sourceforge.net Subject: Re: and nicer too - Re: [PATCH] epoll more scalable than poll Message-ID: <20021101201414.GB1654@bjl1.asuk.net> References: <3DC2BCF5.5010607@kegel.com> <20021101191643.GA1471@bjl1.asuk.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 843 Lines: 18 Charlie Krasic wrote: > 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. ... and close-on-exec. -- Jamie - 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/