From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262713AbVFVHqg (ORCPT ); Wed, 22 Jun 2005 03:46:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262869AbVFVHpx (ORCPT ); Wed, 22 Jun 2005 03:45:53 -0400 Received: from graphe.net ([209.204.138.32]:18624 "EHLO graphe.net") by vger.kernel.org with ESMTP id S262713AbVFVGTN (ORCPT ); Wed, 22 Jun 2005 02:19:13 -0400 Date: Tue, 21 Jun 2005 23:19:02 -0700 (PDT) From: Christoph Lameter X-X-Sender: christoph@graphe.net To: Jeff Garzik cc: Robert Love , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: -mm -> 2.6.13 merge status In-Reply-To: <42B8A51A.8020208@pobox.com> Message-ID: References: <20050620235458.5b437274.akpm@osdl.org> <42B831B4.9020603@pobox.com> <1119368364.3949.236.camel@betsy> <42B8987F.9000607@pobox.com> <42B8A51A.8020208@pobox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: -5.9 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 21 Jun 2005, Jeff Garzik wrote: > > AIO is requiring you to poll and check if I/O is complete. select() does > > Incorrect. The entire point of AIO is that its an async callback system, when > the I/O is complete... just like the kernel's internal I/O request queue > system. Hmmm.. Okay it may work like dnotify. You get some signal and then its up to you to figure out what was going on. Traditionally select() does that all for you and tells you which stream got input.