public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Anton Blanchard <anton@samba.org>
Cc: linux-kernel@vger.kernel.org, hannal@us.ibm.com
Subject: Re: 12 way dbench analysis: 2.5.9, dalloc and fastwalkdcache
Date: Thu, 18 Apr 2002 01:58:18 -0700	[thread overview]
Message-ID: <3CBE8AAA.FD940076@zip.com.au> (raw)
In-Reply-To: <20020418081843.GE4209@krispykreme>

Anton Blanchard wrote:
> 
> Hi,
> 
> Its about time I took to the kernel with the dbench stick. The following
> results were done on a 12 way ppc64 machine with 250MHz cpus. I tested
> 2.5.9, 2.5.9 with Andrew Morton's dalloc work and Hanna Linder's fast
> walk dcache patch. The results can be found at:
> 
> http://samba.org/~anton/linux/2.5.9/
> 

Thanks, Anton.

I should point out that the patches are misnamed - this stuff
has nothing to do with "delayed allocation".  It just started out
that way.

The code Anton tested was the removal of the buffer LRUs and
the buffer hashtable and the introduction of address_space-based
writeback.  That code is >this< close to being ready.  Still
chasing a couple of oddities.

Anton also found a ratcache locking bug.  Patch is under test.

After the writeback changes I plan on:

- A ton of little cleanups
- Add dirty address_spaces to the superblocks, don't find them
  via inodes.
- Assemble BIOs direct against pagecache for buffer-backed
  filesystems - bypass the buffer layer for bulk file I/O.
- All sorts of other stuff.
- Then back onto delayed allocate.  That's item 78 on the
  79-entry todo list...

-

  reply	other threads:[~2002-04-18  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18  8:18 12 way dbench analysis: 2.5.9, dalloc and fastwalkdcache Anton Blanchard
2002-04-18  8:58 ` Andrew Morton [this message]
2002-04-20  0:50   ` Anton Blanchard
2002-04-18 15:17 ` Rusty Russell
2002-04-19  0:32 ` Hanna Linder
2002-04-20  1:00   ` Anton Blanchard
  -- strict thread matches above, loose matches on Subject: below --
2002-04-19 20:11 Paul Menage

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=3CBE8AAA.FD940076@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=anton@samba.org \
    --cc=hannal@us.ibm.com \
    --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