Subject: Re: [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide
	dirty bit]
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Valerie Henson <val_henson@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
       Arjan van de Ven <arjan@linux.intel.com>,
       "Theodore Ts'o" <tytso@mit.edu>, Zach Brown <zach.brown@oracle.com>
In-Reply-To: <20060322011034.GP12571@goober>
References: <20060322011034.GP12571@goober>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Wed, 22 Mar 2006 13:08:50 +0000
Message-Id: <1143032930.3584.5.camel@localhost.localdomain>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1100
Lines: 25

On Maw, 2006-03-21 at 17:10 -0800, Valerie Henson wrote:
> The combination of the orphan inode and preallocation blocks problem
> led me to another idea: create in-memory-only allocation bitmaps for
> both inodes and blocks.  

This was actually done by Interactive Unix long ago to get sane
performance of System 5 file systems which didnt directly use bitmaps.

I suspect you don't need a complete in memory bitmap list however, you
just need an exceptions table of extents that are preallocated.
Furthermore you can bound this by either releasing oldest preallocations
or refusing new ones when you hit some kind of resource bound.

Similarly for inodes, except that you actually have the in memory
exception list in the ext2 inodes in memory already (no inode is orphan
unless open) so you may only need another list pointer to walk the
orphans

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/