From: Rusty Russell Subject: Re: New AIO API Date: Tue, 16 Apr 2013 10:48:35 +0930 Message-ID: <87sj2r6zo4.fsf@rustcorp.com.au> References: <20130412222856.GB31761@localhost> <20130415153113.e91625d754cb60c73e60abff@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-aio@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, lsf-pc@lists.linux-foundation.org, Zach Brown , Felipe Balbi , Greg Kroah-Hartman , Mark Fasheh , Joel Becker , Jens Axboe , Asai Thambi S P , Selvan Mani , Sam Bradshaw , Al Viro , Benjamin LaHaise , Theodore Ts'o To: Andrew Morton , Kent Overstreet Return-path: In-Reply-To: <20130415153113.e91625d754cb60c73e60abff@linux-foundation.org> Sender: owner-linux-aio@kvack.org List-Id: linux-fsdevel.vger.kernel.org Andrew Morton writes: > On Fri, 12 Apr 2013 15:28:56 -0700 Kent Overstreet wrote: >> Those are the main changes (besides adding attributes, of course) that >> I've made so far. >> >> * Get rid of the parallel syscall interface >> >> AIO really shouldn't be implementing its own slightly different >> syscalls; it should be a mechanism for doing syscalls asynchronously. > > Yes. We got about a twelfth of the way there many years ago > (google("syslets")) but it died. A shame. Yeah, letting the current process keep waiting and creating a new one which returns is a fascinating idea, but you really need to swizzle the PIDs so that the "new" one is identical to the old. Otherwise the API is unbearable... Good luck! Rusty. -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to majordomo@kvack.org. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: aart@kvack.org