From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Adrian Hunter <adrian.hunter@nokia.com>,
sct@redhat.com, adilger@sun.com, linux-ext4@vger.kernel.org,
artem.bityutskiy@nokia.com
Subject: Re: [PATCH 1/2] HACK: ext3: mount fast even when recovering
Date: Tue, 14 Jul 2009 18:36:49 -0400 [thread overview]
Message-ID: <20090714223649.GJ10131@mit.edu> (raw)
In-Reply-To: <4A5CFCBD.70305@redhat.com>
On Tue, Jul 14, 2009 at 04:46:37PM -0500, Eric Sandeen wrote:
>
> (whoa, can barriers make something faster? who woulda thunk it)
I sent this reply in response to the first Adrian's first e-mail, that
had bogus e-mail addresses for akpm and sct, so resending it here:
Have you actually benchmarked these patches, ideally with a fixed
filesystem image so the two runs are done requiring exactly the same
number of blocks to recover? We implement ordered I/O in terms of
doing a flush, so it would be surprising to see that a significant
difference in times. Also, it would be useful to do a blktrace before
and after your patches, again with a fixed filesystem image so the
experiment can be carefully controlled.
Regards,
- Ted
next prev parent reply other threads:[~2009-07-14 22:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 14:05 [PATCH 0/2] ext3 HACKs Adrian Hunter
2009-07-14 14:05 ` [PATCH 1/2] HACK: ext3: mount fast even when recovering Adrian Hunter
2009-07-14 21:34 ` Andrew Morton
2009-07-14 21:46 ` Eric Sandeen
2009-07-14 22:36 ` Theodore Tso [this message]
2009-07-15 15:35 ` Adrian Hunter
2009-07-15 5:53 ` Artem Bityutskiy
2009-07-15 15:35 ` Adrian Hunter
2009-07-14 14:06 ` [PATCH 2/2] HACK: do I/O read requests while ext3 journal recovers Adrian Hunter
-- strict thread matches above, loose matches on Subject: below --
2009-07-14 14:02 [PATCH 0/2] ext3 HACKs Adrian Hunter
2009-07-14 14:03 ` [PATCH 1/2] HACK: ext3: mount fast even when recovering Adrian Hunter
2009-07-14 21:22 ` Andreas Dilger
2009-07-15 15:35 ` Adrian Hunter
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=20090714223649.GJ10131@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=artem.bityutskiy@nokia.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sct@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).