From: Daniel Phillips <phillips@phunq.net>
To: "Abhishek Rai" <abhishekrai@google.com>
Cc: "Theodore Tso" <tytso@mit.edu>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Andreas Dilger" <adilger@sun.com>,
linux-kernel@vger.kernel.org, "Ken Chen" <kenchen@google.com>,
"Mike Waychison" <mikew@google.com>,
rohitseth@google.com
Subject: Re: [PATCH] Clustering indirect blocks in Ext3
Date: Fri, 11 Jan 2008 09:05:17 -0800 [thread overview]
Message-ID: <200801110905.18464.phillips@phunq.net> (raw)
In-Reply-To: <d9885f0f0801101317n48e090d6x48f1792c71dc348e@mail.gmail.com>
On Thursday 10 January 2008 13:17, Abhishek Rai wrote:
> Benchmark 5: fsck
> Description: Prepare a newly formated 400GB disk as follows: create
> 200 files of 0.5GB each, 100 files of 1GB each, 40 files of 2.5GB
> ech, and 10 files of 10GB each. fsck command line: fsck -f -n
> 1. vanilla:
> Total: 11m25.3s
> User: 13.4s
> System: 13.2s
> 2. mc:
> Total: 3m11.0s
> User: 13.1s
> System: 12.9s
>
> Note: I'll report results from kernbench and compilebench shortly.
>
> Observations:
> Sequential write performance is much better with metaclustering than
> with vanilla. To better understand it, I ran the same benchmark with
> the new code but with the metaclustering option turned off and I got
> the same performance as vanilla which makes me believe that there is
> something about metaclustering that helps write performance though I
> don't have a very good handle of what that thing might be.
Your results are very impressive. In my opinion, the sooner this goes
in, the better, since everybody hates waiting for fsck. The only issue
that jumps out at me is, the patch is big and changes a significant
amount of Ext3 code outside of the metacluster path, which is not a bad
thing except that these changes are going to need to be tested fairly
heavily.
The way to do that is, put a big [CALL FOR TESTING] in your subject line
the next time you post, and use an attention-getting subject line
like "Make Ext3 fsck way faster". Diff the patch against the latest
stable kernel to make things as easy as possible for the people who are
hopefully going to download your patch, try it, and report their
results.
The other way is just to ask Andrew to put it in -mm when you feel
ready, but your chances are much better if you already have people
sending in mails saying how great your patch is.
Another thing you might consider is a port to Ext4. After all, the
world has waited this long for your patch, so it can likely survive
waiting a little longer.
You somehow seem to have missed attracting the attention of Jon Corbet,
a rare occurrence for a patch of this significance. With the subject
line modified as above, you are more likely to get the attention you
deserve. Good luck!
Regards,
Daniel
next prev parent reply other threads:[~2008-01-11 17:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 5:02 [PATCH] Clustering indirect blocks in Ext3 Abhishek Rai
2007-11-16 7:02 ` Andrew Morton
2007-11-16 7:37 ` Matt Mackall
2007-11-18 15:52 ` Abhishek Rai
2007-11-18 20:47 ` Matt Mackall
2007-11-19 10:34 ` Kyungmin Park
2007-11-20 20:25 ` John Stoffel
2007-11-16 11:28 ` Andreas Dilger
2007-11-16 21:11 ` Theodore Tso
2007-11-17 0:25 ` Abhishek Rai
2007-11-17 2:58 ` Theodore Tso
2007-11-17 8:58 ` Abhishek Rai
2007-12-21 14:15 ` Abhishek Rai
2008-01-10 21:17 ` Abhishek Rai
2008-01-11 17:05 ` Daniel Phillips [this message]
2008-01-12 0:04 ` Andrew Morton
2008-01-12 6:05 ` Daniel Phillips
2008-01-13 5:06 ` Abhishek Rai
2007-11-16 22:27 ` Abhishek Rai
[not found] <9q1CT-82L-3@gated-at.bofh.it>
[not found] ` <9q3v2-2Br-3@gated-at.bofh.it>
[not found] ` <9qgLE-7ds-21@gated-at.bofh.it>
[not found] ` <9qjJx-3wE-9@gated-at.bofh.it>
[not found] ` <9qm4D-70Q-1@gated-at.bofh.it>
[not found] ` <9CQTt-7cr-27@gated-at.bofh.it>
[not found] ` <9KcYS-46E-27@gated-at.bofh.it>
2008-01-11 14:12 ` Bodo Eggert
2008-01-11 14:49 ` Abhishek Rai
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=200801110905.18464.phillips@phunq.net \
--to=phillips@phunq.net \
--cc=abhishekrai@google.com \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=rohitseth@google.com \
--cc=tytso@mit.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