From: Andrea Arcangeli <andrea@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Benjamin LaHaise <bcrl@redhat.com>,
linux-kernel@vger.kernel.org, linux-aio@kvack.org
Subject: Re: async-io API registration for 2.5.29
Date: Tue, 30 Jul 2002 18:49:35 +0200 [thread overview]
Message-ID: <20020730164935.GI1181@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0207300633140.2599-100000@home.transmeta.com>
On Tue, Jul 30, 2002 at 06:34:53AM -0700, Linus Torvalds wrote:
>
>
> On Tue, 30 Jul 2002, Andrea Arcangeli wrote:
> >
> > this patch against 2.5.29 adds the async-io API as from latest Ben's
> > patch.
>
> Why not make the io_submit system call number 251 like it apparently is
> already in 2.4.x? We're really close to it anyway, so if you just re-order
> the system calls a bit (and leave 250 as sys_ni_syscall), you're basically
> there.
>
> Other than that it looks good.
thank you very much for checking it. Since Ben asked for waiting his
patch you can reject may patch, that's really fine with me as far as it
doesn't take months for his patch to showup. my patch is in perfect sync
with his latest code on the web.
as said I never claimed current API is stupid as Christph understood, I
said I'd preferred a sys_aio_read/write/fsync etc... but I could live
fine with sys_io_submit too, it wasn't too bad enough to make me rewrite
it.
With my patch I mainly wanted to raise eyes on this issue so we can
hopefully get an API registered in a few weeks in mainline. I'm
completely flexbile to rewrite the API too if anybody find good reasons
for it (or if you say, sys_io_submit is too ugly please change to
sys_aio_read/write/etc..).
As Ben said the API is the only thing that is been mostly stable so far,
this is one more reason I felt this is the right way to proceed instead
of building the dynamic syscall slowdown overhead layer that as best
(unsure for sys_io_sumbit 250) is forward binary compatible with 2.5 by
pure luck.
thanks,
Andrea
prev parent reply other threads:[~2002-07-30 16:45 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 5:41 async-io API registration for 2.5.29 Andrea Arcangeli
2002-07-30 8:11 ` Christoph Hellwig
2002-07-30 13:40 ` Linus Torvalds
2002-07-30 13:52 ` Benjamin LaHaise
2002-07-30 16:43 ` Andrea Arcangeli
2002-07-30 16:59 ` Benjamin LaHaise
2002-07-30 19:10 ` Jeff Dike
2002-07-30 18:09 ` Benjamin LaHaise
2002-07-30 18:15 ` Linus Torvalds
2002-07-30 18:31 ` Benjamin LaHaise
2002-07-30 20:57 ` Jeff Dike
2002-07-30 20:47 ` Jeff Dike
2002-07-30 21:26 ` Andrea Arcangeli
2002-07-30 10:50 ` Rik van Riel
2002-07-30 12:49 ` Benjamin LaHaise
2002-07-30 13:29 ` Suparna Bhattacharya
2002-07-30 21:41 ` Andrea Arcangeli
2002-07-30 21:54 ` [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29) Benjamin LaHaise
2002-07-31 0:44 ` Andrea Arcangeli
2002-07-31 14:46 ` Benjamin LaHaise
2002-07-31 16:31 ` Charles 'Buck' Krasic
2002-08-01 10:30 ` Pavel Machek
2002-08-01 14:47 ` Benjamin LaHaise
2002-08-01 15:00 ` Chris Friesen
2002-08-01 16:09 ` Linus Torvalds
2002-08-01 17:30 ` Alan Cox
2002-08-01 16:30 ` Linus Torvalds
2002-08-01 16:41 ` [rfc] aio-core for 2.5.29 (Re: async-io API registration for2.5.29) Chris Friesen
2002-08-01 18:01 ` [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29) Benjamin LaHaise
2002-08-15 23:54 ` aio-core why not using SuS? [Re: [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29)] Andrea Arcangeli
2002-08-16 1:42 ` Benjamin LaHaise
2002-08-16 1:57 ` Andrea Arcangeli
2002-08-16 2:00 ` Benjamin LaHaise
2002-08-16 2:08 ` Linus Torvalds
2002-08-16 2:16 ` Benjamin LaHaise
2002-08-16 2:40 ` Andrea Arcangeli
2002-08-16 3:43 ` Linus Torvalds
2002-08-16 3:50 ` Linus Torvalds
2002-08-16 4:47 ` William Lee Irwin III
2002-08-17 3:46 ` Martin J. Bligh
2002-08-17 4:00 ` Linus Torvalds
2002-08-17 4:15 ` Martin J. Bligh
2002-08-17 4:46 ` Linus Torvalds
2001-11-02 5:12 ` Pavel Machek
2002-08-17 5:04 ` Linus Torvalds
2002-08-17 5:24 ` lots of mem on 32 bit machines (was: aio-core why not using SuS?) Martin J. Bligh
2002-08-17 5:12 ` aio-core why not using SuS? [Re: [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29)] Martin J. Bligh
2002-08-17 17:02 ` Linus Torvalds
2002-08-17 21:27 ` 32 bit arch with lots of RAM Martin J. Bligh
2002-08-22 16:30 ` Andrea Arcangeli
2002-08-22 16:36 ` Martin J. Bligh
2002-08-22 16:15 ` aio-core why not using SuS? [Re: [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29)] Andrea Arcangeli
2002-08-22 16:12 ` Andrea Arcangeli
2002-08-20 0:35 ` Ingo Molnar
2002-08-17 4:36 ` William Lee Irwin III
2002-08-16 2:32 ` Rik van Riel
2002-08-16 2:32 ` Andrea Arcangeli
2002-08-16 9:39 ` Suparna Bhattacharya
2002-08-16 10:03 ` Andrea Arcangeli
2002-08-16 11:23 ` Suparna Bhattacharya
2002-08-16 11:28 ` Suparna Bhattacharya
2002-08-16 13:49 ` Dan Kegel
2002-09-02 18:40 ` Andrea Arcangeli
2002-09-03 12:04 ` aio-core in 2.5 - io_queue_wait and io_getevents Suparna Bhattacharya
2002-09-05 5:21 ` aio-core why not using SuS? [Re: [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29)] Benjamin LaHaise
2002-08-16 13:43 ` Dan Kegel
2002-08-16 14:21 ` Jamie Lokier
2002-08-16 14:42 ` Benjamin LaHaise
2002-08-16 15:40 ` John Gardiner Myers
2002-08-23 16:11 ` aio-core why not using SuS? [Re: [rfc] aio-core for 2.5.29 (Re:async-io " Dan Kegel
2002-08-16 1:53 ` aio-core why not using SuS? [Re: [rfc] aio-core for 2.5.29 (Re: async-io " Dan Kegel
2002-08-01 19:18 ` [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29) Chris Wedgwood
2002-08-01 19:25 ` Linus Torvalds
2002-08-01 19:31 ` Chris Wedgwood
2002-08-02 8:24 ` Pavel Machek
2002-08-02 11:59 ` Alan Cox
2002-08-02 15:56 ` Linus Torvalds
2002-07-31 1:20 ` async-io API registration for 2.5.29 Rik van Riel
2002-07-31 1:32 ` Andrea Arcangeli
2002-07-31 8:25 ` Christoph Hellwig
2002-07-31 13:19 ` Andrea Arcangeli
2002-07-30 13:34 ` Linus Torvalds
2002-07-30 16:49 ` Andrea Arcangeli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020730164935.GI1181@dualathlon.random \
--to=andrea@suse.de \
--cc=bcrl@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox