From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Hunter Adrian (Nokia-D/Helsinki)" <adrian.hunter@nokia.com>,
"sct@redhat.com" <sct@redhat.com>,
"adilger@sun.com" <adilger@sun.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/2] HACK: ext3: mount fast even when recovering
Date: Wed, 15 Jul 2009 08:53:55 +0300 [thread overview]
Message-ID: <4A5D6EF3.9050200@nokia.com> (raw)
In-Reply-To: <20090714143449.cae624c8.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Tue, 14 Jul 2009 17:05:54 +0300
> Adrian Hunter <adrian.hunter@nokia.com> wrote:
>
>> Speed up ext3 recovery mount time by not sync'ing the
>> block device. Instead place all dirty buffers into the
>> I/O queue and add a write barrier. This ensures that
>> no subsequent write will reach the disk before all the
>> recovery writes, but that we do not have to wait for the
>> I/O.
>>
>> Note that ext3 reads sectors the correct way: through the
>> buffer cache, so there is no risk of reading old metadata.
>
> hm. The change seems reasonable to me. afaict it leaves no timing
> windows during which another crash could muck things up.
In fact it was not very easy to persuade Adrian to submit
these patches to public because he thinks they are hacks and
not useful for anyone but us.
FYI, we are trying to check how ext3 works on MMC, which
is very slow on random writes, and Adrian come up with
these patches to speed up ext3 recovery.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-07-15 5:54 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
2009-07-15 15:35 ` Adrian Hunter
2009-07-15 5:53 ` Artem Bityutskiy [this message]
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=4A5D6EF3.9050200@nokia.com \
--to=artem.bityutskiy@nokia.com \
--cc=adilger@sun.com \
--cc=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.