Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932475AbWCFXiS (ORCPT ); Mon, 6 Mar 2006 18:38:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932477AbWCFXiS (ORCPT ); Mon, 6 Mar 2006 18:38:18 -0500 Received: from kanga.kvack.org ([66.96.29.28]:5312 "EHLO kanga.kvack.org") by vger.kernel.org with ESMTP id S932475AbWCFXiS (ORCPT ); Mon, 6 Mar 2006 18:38:18 -0500 Date: Mon, 6 Mar 2006 18:33:00 -0500 From: Benjamin LaHaise To: Ulrich Drepper Cc: Dan Aloni , Linux Kernel List Subject: Re: Status of AIO Message-ID: <20060306233300.GR20768@kvack.org> References: <20060306062402.GA25284@localdomain> <20060306211854.GM20768@kvack.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 958 Lines: 20 On Mon, Mar 06, 2006 at 02:53:07PM -0800, Ulrich Drepper wrote: > I don't think the POSIX AIO nor the kernel AIO interfaces are suitable > for sockets, at least the way we can expect network traffic to be > handled in the near future. Some more radical approaches are needed. > I'll have some proposals which will be part of the talk I have at OLS. Oh? I've always envisioned that network AIO would be able to use O_DIRECT style zero copy transmit, and something like I/O AT on the receive side. The in kernel API provides a lightweight event mechanism that should work ideally for this purpose. -ben -- "Time is of no importance, Mr. President, only life is important." Don't Email: . - 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/