From: Adrian Hunter <adrian.hunter@nokia.com>
To: Andrew.Morton.akpm@linux-foundation.org,
Andreas.Dilger.adilger@sun.com, Stephen.Tweedie.sct@redhat.com
Cc: Artem Bityutskiy <artem.bityutskiy@nokia.com>,
linux-ext4@vger.kernel.org,
Adrian Hunter <adrian.hunter@nokia.com>
Subject: [PATCH 0/2] ext3 HACKs
Date: Tue, 14 Jul 2009 17:02:53 +0300 [thread overview]
Message-ID: <20090714140253.25993.64525.sendpatchset@ahunter-tower> (raw)
Hi
We are using linux 2.6.28 and we have a situation where ext3
can take 30-60 seconds to mount.
The cause is the underlying device has extremely poor random
write speed (several orders of magnitude slower than sequential
write speed), and journal recovery can involve many small random
writes.
To alleviate this situation somewhat, I have two moderately ugly
hacks:
HACK 1: ext3: mount fast even when recovering
HACK 2: do I/O read requests while ext3 journal recovers
HACK 1 uses a I/O barrier in place of waiting for recovery I/O to be
flushed.
HACK 2 crudely throws I/O read requests to the front of the dispatch
queue until the I/O barrier from HACK 1 is reached.
If you can spare a moment to glance at these hacks and notice
any obvious flaws, or suggest a better alternative, it would be
greatly appreciated.
Regards
Adrian Hunter
next reply other threads:[~2009-07-14 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 14:02 Adrian Hunter [this message]
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
2009-07-14 14:03 ` [PATCH 2/2] HACK: do I/O read requests while ext3 journal recovers Adrian Hunter
2009-07-14 21:26 ` Andreas Dilger
2009-07-15 15:35 ` Adrian Hunter
2009-07-14 15:51 ` [PATCH 0/2] ext3 HACKs Theodore Tso
-- strict thread matches above, loose matches on Subject: below --
2009-07-14 14:05 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=20090714140253.25993.64525.sendpatchset@ahunter-tower \
--to=adrian.hunter@nokia.com \
--cc=Andreas.Dilger.adilger@sun.com \
--cc=Andrew.Morton.akpm@linux-foundation.org \
--cc=Stephen.Tweedie.sct@redhat.com \
--cc=artem.bityutskiy@nokia.com \
--cc=linux-ext4@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