public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Benjamin LaHaise <bcrl@redhat.com>,
	ak@suse.de, viro@math.psu.edu, jgmyers@netscape.com
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org,
	lse-tech@lists.sourceforge.net
Subject: Writeup on AIO design (uploaded)
Date: Wed, 30 Jan 2002 20:13:04 +0530	[thread overview]
Message-ID: <20020130201304.A1859@in.ibm.com> (raw)
In-Reply-To: <20020129205620.A1886@in.ibm.com> <20020129225600.A10775@redhat.com> <20020130143215.B1378@in.ibm.com>
In-Reply-To: <20020130143215.B1378@in.ibm.com>; from suparna@in.ibm.com on Wed, Jan 30, 2002 at 02:32:15PM +0530

Hello,

I have just uploaded the aio design notes to:
 http://lse.sourcefourge.net/io/aionotes.txt

Thanks to all those who helped with inputs and reviews of the interim 
drafts.

The writeup attempts to bring out some of the interesting design issues 
and discuss the solutions to those issues and the approach taken in 
Ben's design, and touches on the ideas for addressing some of the pending 
issues, todo items and potential enhancements. It also looks at some of
these aspects in the context of other implementations that exist or have 
been attempted on Linux (SGI kaio, Univ of Winsconsin-Madison's BAIO, 
Andi Kleen's early prototype), and the AIO related interfaces available 
on other OS's (POSIX aio, NT IOCPs, BSD kqueues), and also the DAFS api 
specifications. 

This was written with the intention of triggering discussions (though
this writeup wouldn't have been possible without all the discusions we've
already had :)). 

So please do share your insights, perspectives and comments. 

All the more so, if you already have a good understanding the aio 
design ! 

For those who are new to aio:
The focus here is only the in-kernel aio design, so you won't find much 
about actually using aio (Dan Kegel's page might be a better
place to start on that). There should, however, be some insights,
and pointers to the in-kernel primitives introduced as part of aio,
say, if you intend to implement your own async state machine (for some 
reason !). However, the writeup does not get into low level details and 
is not intended to be a substitute for looking at the code :). 
It should help you follow the code more easily though (I hope).

Regards
Suparna


           reply	other threads:[~2002-01-30 14:41 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20020130143215.B1378@in.ibm.com>]

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=20020130201304.A1859@in.ibm.com \
    --to=suparna@in.ibm.com \
    --cc=ak@suse.de \
    --cc=bcrl@redhat.com \
    --cc=jgmyers@netscape.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=viro@math.psu.edu \
    /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