public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suparna Bhattacharya <suparna@in.ibm.com>
To: akpm@osdl.org, linux-aio@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: Latest AIO patchset
Date: Tue, 24 Feb 2004 21:33:41 +0530	[thread overview]
Message-ID: <20040224160341.GA11739@in.ibm.com> (raw)


The latest set of AIO patches are being maintained at:
http://www.kernel.org/pub/linux/kernel/people/suparna/aio/

The patches have been reduced to a minimal set that addresses
the most relevant blocking points. Please let me know if you
think there is a case for bringing in any of the additional 
patches.
(The patches need to be applied in the order mention in the 
'series' file)

A new addition to the patchset is Chris Mason's nice and simple
implementation of AIO support for pipes using the retry 
infrastructure. He also fixed some problems in the AIO cancel
logic to make it play well with retries.

Besides this and some re-organization and cleaning up, there
are a couple of changes since the last set of patches in -mm, that
are worth a mention:

- Upfront readahead is now clipped to the readahead limit for
  the device (ra_pages) and happens only for AIO. This helps
  address the sendfile regression seen by Felix von Leitner.
  If your AIO read requests are likely to exceed the default 
  readahead size, then use hdparm -a <new size> to tune it.
  The patchset also currently includes Ram Pai's adaptive
  lazy readahead code which is required for good streaming AIO
  read performance.
- David Brownell's suggestion of enabling the fops to set up
  their own retry methods. This should make his USB gadgetfs
  AIO patch co-exist smoothly with fsaio.

Some basic results are up comparing streaming non-cached random 
AIO read/write throughputs for a single ext3 file using aio-stress 
for various io sizes with and without these patches, and also 
comparsions with O_DIRECT AIO throughputs. The short summary has
been a doubling of throughput using the fsaio patches, which is
also close to the results seen with O_DIRECT AIO.

As usual feedback, bug fixes, test results etc are welcome.

Regards
Suparna

-- 
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India


             reply	other threads:[~2004-02-24 10:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 16:03 Suparna Bhattacharya [this message]
2004-02-24 11:02 ` kexec "problem" Carlos Silva
2004-02-24 17:10   ` Randy.Dunlap
2004-02-24 17:24     ` Carlos Silva
2004-02-27  0:54   ` kexec "problem" [and patch updates] Randy.Dunlap
2004-02-27  8:00     ` [Fastboot] " Eric W. Biederman
2004-02-27 19:32       ` Randy.Dunlap
2004-02-28 10:41         ` Eric W. Biederman
2004-03-04 13:03           ` Hariprasad Nellitheertha
2004-03-08  0:32             ` Eric W. Biederman
2004-03-08 18:35             ` Randy.Dunlap
2004-02-25 18:45 ` Latest AIO patchset Hayim Shaul
2004-02-26  0:27   ` Benjamin LaHaise
2004-02-26 13:30     ` Hayim Shaul
2004-02-26 16:45       ` Daniel McNeil

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=20040224160341.GA11739@in.ibm.com \
    --to=suparna@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    /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