From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Abhishek Rai <abhishekrai@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CALL FOR TESTING] Make Ext3 fsck way faster [2.6.23.13]
Date: Tue, 15 Jan 2008 15:47:07 -0800 [thread overview]
Message-ID: <478D45FB.9050209@goop.org> (raw)
In-Reply-To: <200801140811.44191.abhishekrai@google.com>
Abhishek Rai wrote:
> Hi,
>
> (Sorry for the inconvenience caused due to previous misformatted patch, I've most definitely figured out the problem this time. Thanks Michael, Daniel, and Ingo for your help.)
>
> This patch speeds up e2fsck on Ext3 significantly using a technique called Metaclustering. Metaclustering is being discussed on LKML in some other threads, here is the latest patch against the 2.6.23.13 stable kernel, any help in testing and evaluating this will be greatly appreciated! While I'd direct anyone interested in details of metaclustering to other LKML threads discussing it, I've enclosed a brief description here:
>
> Metaclustering refers to storing indirect blocks in clusters on a per-group basis instead of spreading them out along with the data blocks.
Cool!
Sounds like this should also make unlink of large files faster too,
which is a much more saleable win. At Digeo we always had the problem
that deleting a multi-GB PVR file would thrash the disk to death and
give everyone else ~0 throughput.
J
next prev parent reply other threads:[~2008-01-15 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 13:11 [CALL FOR TESTING] Make Ext3 fsck way faster [2.6.23.13] Abhishek Rai
2008-01-15 23:47 ` Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-13 5:41 Abhishek Rai
2008-01-13 9:14 ` Michael Gerdau
2008-01-14 1:09 ` Daniel Phillips
2008-01-14 11:06 ` Ingo Molnar
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=478D45FB.9050209@goop.org \
--to=jeremy@goop.org \
--cc=abhishekrai@google.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