linux-ext4 - Re: [PATCH 2/2] HACK: do I/O read requests while ext3 journal recovers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 15 Jul 2009 18:35:41 +0300
From:	Adrian Hunter <adrian.hunter@...ia.com>
To:	Andreas Dilger <adilger@....com>
CC:	"Andrew.Morton.akpm@...ux-foundation.org" 
	<Andrew.Morton.akpm@...ux-foundation.org>,
	"Andreas.Dilger.adilger@....com" <Andreas.Dilger.adilger@....com>,
	"Stephen.Tweedie.sct@...hat.com" <Stephen.Tweedie.sct@...hat.com>,
	"Bityutskiy Artem (Nokia-D/Helsinki)" <Artem.Bityutskiy@...ia.com>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH 2/2] HACK: do I/O read requests while ext3 journal	recovers

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.


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html