From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422783AbXCOAcc (ORCPT ); Wed, 14 Mar 2007 20:32:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1422784AbXCOAcc (ORCPT ); Wed, 14 Mar 2007 20:32:32 -0400 Received: from x35.xmailserver.org ([64.71.152.41]:42511 "EHLO x35.xmailserver.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422783AbXCOAcb (ORCPT ); Wed, 14 Mar 2007 20:32:31 -0400 X-AuthUser: davidel@xmailserver.org Date: Wed, 14 Mar 2007 17:27:33 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@alien.or.mcafeemobile.com To: Benjamin LaHaise cc: Linux Kernel Mailing List , Andrew Morton , Linus Torvalds , Ingo Molnar , Suparna Bhattacharya , Zach Brown Subject: Re: [patch 13/13] signalfd/timerfd/asyncfd v5 - KAIO asyncfd support (example/maybe-broken) ... In-Reply-To: Message-ID: References: <20070314231920.GB1246@kvack.org> <20070314234208.GC1246@kvack.org> <20070315000212.GD1246@kvack.org> X-GPG-FINGRPRINT: CFAE 5BEE FD36 F65E E640 56FE 0974 BF23 270F 474E X-GPG-PUBLIC_KEY: http://www.xmailserver.org/davidel.asc MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 14 Mar 2007, Davide Libenzi wrote: > On Wed, 14 Mar 2007, Benjamin LaHaise wrote: > > > On Wed, Mar 14, 2007 at 04:41:58PM -0700, Davide Libenzi wrote: > > > Yeah, of course. I do not plan revolutions. Just asking if it's a possible > > > thing to do. I can mlock the userspace ring, if imposing that burden over > > > aio_complete() is seen as too heavy. > > > > I'm not sure I follow what you're doing -- why isn't asyncfd merely calling > > io_getevents() instead of reinventing everything the ringbuffer does? The > > aio ringbuffer is already locked in memory. Fwiw, the aio ringbuffer was > > originally wired up to a file descriptor, but that gave way to the actual > > syscall in order to enforce proper typechecking and typical usage scenarios > > with timeouts. > > The purpose of asyncfd is to provide a pollable (by the mean of > f_op->poll) device that can be hosted inside a standard select/poll/epoll > wait subsystem, and that, at the same time, provide a zero-copy way for > kernel code (KAIO and syslets/threadlets were my thought) to deliver > results to userspace. But, yeah. It can end up calling io_getevents() instead of doing it's own thing. That'd make it even slimmer ;) - Davide