From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933874AbcALJx3 (ORCPT ); Tue, 12 Jan 2016 04:53:29 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:34058 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932704AbcALJxY (ORCPT ); Tue, 12 Jan 2016 04:53:24 -0500 Date: Tue, 12 Jan 2016 10:53:19 +0100 From: Ingo Molnar To: Linus Torvalds Cc: Benjamin LaHaise , linux-aio@kvack.org, linux-fsdevel , Linux Kernel Mailing List , Linux API , linux-mm , Alexander Viro , Andrew Morton Subject: Re: [PATCH 09/13] aio: add support for async openat() Message-ID: <20160112095319.GA20597@gmail.com> References: <150a0b4905f1d7274b4c2c7f5e3f4d8df5dda1d7.1452549431.git.bcrl@kvack.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Linus Torvalds wrote: > What do you think? Do you think it might be possible to aim for a generic "do > system call asynchronously" model instead? > > I'm adding Ingo the to cc, because I think Ingo had a "run this list of system > calls" patch at one point - in order to avoid system call overhead. I don't > think that was very interesting (because system call overhead is seldom all that > noticeable for any interesting system calls), but with the "let's do the list > asynchronously" addition it might be much more intriguing. Ingo, do I remember > correctly that it was you? I might be confused about who wrote that patch, and I > can't find it now. Yeah, it was the whole 'syslets' and 'threadlets' stuff - I had both implemented and prototyped into a 'list directory entries asynchronously' testcase. Threadlets was pretty close to what you are suggesting now. Here's a very good (as usual!) writeup from LWN: https://lwn.net/Articles/223899/ Thanks, Ingo From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 12 Jan 2016 10:53:19 +0100 From: Ingo Molnar To: Linus Torvalds Cc: Benjamin LaHaise , linux-aio@kvack.org, linux-fsdevel , Linux Kernel Mailing List , Linux API , linux-mm , Alexander Viro , Andrew Morton Subject: Re: [PATCH 09/13] aio: add support for async openat() Message-ID: <20160112095319.GA20597@gmail.com> References: <150a0b4905f1d7274b4c2c7f5e3f4d8df5dda1d7.1452549431.git.bcrl@kvack.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: * Linus Torvalds wrote: > What do you think? Do you think it might be possible to aim for a generic "do > system call asynchronously" model instead? > > I'm adding Ingo the to cc, because I think Ingo had a "run this list of system > calls" patch at one point - in order to avoid system call overhead. I don't > think that was very interesting (because system call overhead is seldom all that > noticeable for any interesting system calls), but with the "let's do the list > asynchronously" addition it might be much more intriguing. Ingo, do I remember > correctly that it was you? I might be confused about who wrote that patch, and I > can't find it now. Yeah, it was the whole 'syslets' and 'threadlets' stuff - I had both implemented and prototyped into a 'list directory entries asynchronously' testcase. Threadlets was pretty close to what you are suggesting now. Here's a very good (as usual!) writeup from LWN: https://lwn.net/Articles/223899/ Thanks, Ingo -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH 09/13] aio: add support for async openat() Date: Tue, 12 Jan 2016 10:53:19 +0100 Message-ID: <20160112095319.GA20597@gmail.com> References: <150a0b4905f1d7274b4c2c7f5e3f4d8df5dda1d7.1452549431.git.bcrl@kvack.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: owner-linux-aio@kvack.org To: Linus Torvalds Cc: Benjamin LaHaise , linux-aio@kvack.org, linux-fsdevel , Linux Kernel Mailing List , Linux API , linux-mm , Alexander Viro , Andrew Morton List-Id: linux-api@vger.kernel.org * Linus Torvalds wrote: > What do you think? Do you think it might be possible to aim for a generic "do > system call asynchronously" model instead? > > I'm adding Ingo the to cc, because I think Ingo had a "run this list of system > calls" patch at one point - in order to avoid system call overhead. I don't > think that was very interesting (because system call overhead is seldom all that > noticeable for any interesting system calls), but with the "let's do the list > asynchronously" addition it might be much more intriguing. Ingo, do I remember > correctly that it was you? I might be confused about who wrote that patch, and I > can't find it now. Yeah, it was the whole 'syslets' and 'threadlets' stuff - I had both implemented and prototyped into a 'list directory entries asynchronously' testcase. Threadlets was pretty close to what you are suggesting now. Here's a very good (as usual!) writeup from LWN: https://lwn.net/Articles/223899/ Thanks, Ingo -- 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