Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 31 Oct 2002 19:26:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 31 Oct 2002 19:26:36 -0500 Received: from bjl1.asuk.net.64.29.81.in-addr.arpa ([81.29.64.88]:11955 "EHLO bjl1.asuk.net") by vger.kernel.org with ESMTP id ; Thu, 31 Oct 2002 19:26:36 -0500 Date: Fri, 1 Nov 2002 00:32:38 +0000 From: Jamie Lokier To: Rusty Russell Cc: Alan Cox , davidel@xmailserver.org, linux-kernel@vger.kernel.org, linux-aio@kvack.org, lse-tech@lists.sourceforge.net, torvalds@transmeta.com, akpm@digeo.com Subject: Re: Unifying epoll,aio,futexes etc. (What I really want from epoll) Message-ID: <20021101003238.GA30865@bjl1.asuk.net> References: <20021031005259.GA25651@bjl1.asuk.net> <20021031154112.GB27801@bjl1.asuk.net> <1036082758.8575.81.camel@irongate.swansea.linux.org.uk> <20021101090034.42e207e5.rusty@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021101090034.42e207e5.rusty@rustcorp.com.au> User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 766 Lines: 19 Rusty Russell wrote: > I think a naive implementation of futex_set_wait would look like: Vaguely. We are looking for something with the queue-like semantics of epoll and rt-signals: persistent (as opposed to one-shot) listening, ordered delivery of events, scalable listening to thousands at once (without the poll/select O(n) problem). > Not sure I get the point about livelock though: deadlock is possible if > apps seek multiple locks at once without care, of course. I'm not sure what Alan meant either. -- 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/