linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@nokia.com>
To: Andreas Dilger <adilger@sun.com>
Cc: "Andrew.Morton.akpm@linux-foundation.org"
	<Andrew.Morton.akpm@linux-foundation.org>,
	"Andreas.Dilger.adilger@sun.com" <Andreas.Dilger.adilger@sun.com>,
	"Stephen.Tweedie.sct@redhat.com" <Stephen.Tweedie.sct@redhat.com>,
	"Bityutskiy Artem (Nokia-D/Helsinki)"
	<Artem.Bityutskiy@nokia.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 2/2] HACK: do I/O read requests while ext3 journal	recovers
Date: Wed, 15 Jul 2009 18:35:41 +0300	[thread overview]
Message-ID: <4A5DF74D.7010100@nokia.com> (raw)
In-Reply-To: <20090714212625.GE4829@webber.adilger.int>

Andreas Dilger wrote:
> On Jul 14, 2009  17:03 +0300, Adrian Hunter wrote:
>> The ext3 journal can take a long time to recover at mount
>> time.  That was partially fixed by placing a barrier into
>> the I/O queue and then not waiting for the actual I/O to
>> complete.
> 
> Note that you can also reduce the journal recovery time by
> reducing the size of the journal.  Having a large journal
> is needed for getting good performance with lots of updates
> at high speeds.  If you aren't doing a large amount of
> filesystem IO (which I'd guess for an embedded device, assuming
> you are using it for that), then you could reduce the size of
> the journal to the minimum (1000 blocks) and this will also
> reduce the recovery time correspondingly.

Yes that may help, although the number of blocks involved is
fairly small.



  reply	other threads:[~2009-07-15 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
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 [this message]
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
2009-07-14 14:06 ` [PATCH 2/2] HACK: do I/O read requests while ext3 journal recovers 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=4A5DF74D.7010100@nokia.com \
    --to=adrian.hunter@nokia.com \
    --cc=Andreas.Dilger.adilger@sun.com \
    --cc=Andrew.Morton.akpm@linux-foundation.org \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=Stephen.Tweedie.sct@redhat.com \
    --cc=adilger@sun.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;
as well as URLs for NNTP newsgroup(s).