Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 21 Oct 2002 12:37:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 21 Oct 2002 12:37:54 -0400 Received: from pc1-cwma1-5-cust42.swa.cable.ntl.com ([80.5.120.42]:63412 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Mon, 21 Oct 2002 12:37:52 -0400 Subject: Re: [PATCH] async poll for 2.5 From: Alan Cox To: John Gardiner Myers Cc: "Charles 'Buck' Krasic" , Davide Libenzi , Benjamin LaHaise , Dan Kegel , Shailabh Nagar , Linux Kernel Mailing List , linux-aio , Andrew Morton , David Miller , Linus Torvalds , Stephen Tweedie In-Reply-To: <3DADB020.4060506@netscape.com> References: <3DACA5E4.7090509@netscape.com> <3DADB020.4060506@netscape.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 21 Oct 2002 17:58:17 +0100 Message-Id: <1035219498.27318.205.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 984 Lines: 20 On Wed, 2002-10-16 at 19:29, John Gardiner Myers wrote: > Better to fix the API. The kernel has more information than user space > and can do a better job. In the kernel, the problem can be fixed once > and for all, not over and over again in each different wrapper library. > It's not even as if the change would break programs correctly written > to the old API, not that we particularly care about programs written to > the old API. I think a chunk of the poll scaling problem is better addressed by futexes. If I can say "this futex list for this fd for events X Y and Z" I can construct almost all the efficient stuff I need out of the futex interfaces, much like doing it with SIGIO setting flags but a lot less clocks Alan - 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/