From: Andrew Morton <akpm@zip.com.au>
To: rwhron@earthlink.net
Cc: jjs@lexus.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.8 final - another data point
Date: Tue, 16 Apr 2002 15:02:21 -0700 [thread overview]
Message-ID: <3CBC9F6D.3F4E6579@zip.com.au> (raw)
In-Reply-To: <20020416174827.A1845@rushmore>
rwhron@earthlink.net wrote:
>
> >>Running dbench 128 on ext2 mounted with delalloc and Andrew's
> >>patches from http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.8/
> >>was 7.5x faster than 2.5.8 vanilla and 1.5x faster than
>
> > Wow, good stuff - I'll have to pull those down
>
> Hmm, I had to run e2fsck -f twice on the filesystem that ran
> dbench, tiobench, bonnie++ on nfs, and osdb. The filesystem
> was showing 52% used and is normally 1% used before/after
> testing. No big files on the fs. The directory where
> bonnie++ on nfs runs had some temporary directories that
> were not deletable. A bunch of files/directories were in
> lost+found after e2fsck. After removing the files, the
> fs was back to 1% used.
>
ho-hum. Presumably an unreservepage() got lost somewhere
in the diff shuffling.
All I'm doing with the delayed-allocation code at present
is keeping the diffs up to date. I haven't even compiled
that stuff for over a week. All work at present is against
dallocbase-70-writeback. It's probably not a good use of
your time to test anything beyond that. Sorry about that.
I'll leave the later diffs available so anyone who's interested
can see the multipage bio assembly stuff, but "dont use".
-
next prev parent reply other threads:[~2002-04-16 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 21:48 2.5.8 final - another data point rwhron
2002-04-16 22:02 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-16 12:42 rwhron
2002-04-16 18:31 ` J Sloan
2002-04-14 21:06 2.5.8 final - J Sloan
2002-04-15 5:46 ` 2.5.8 final - another data point J Sloan
2002-04-15 6:35 ` J Sloan
2002-04-15 7:27 ` Andrew Morton
2002-04-15 8:02 ` J Sloan
2002-04-15 7:18 ` Andrew Morton
2002-04-15 8:14 ` J Sloan
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=3CBC9F6D.3F4E6579@zip.com.au \
--to=akpm@zip.com.au \
--cc=jjs@lexus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhron@earthlink.net \
/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