Messages in this thread | | | Subject | Re: [Ext2-devel] Re: [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit] | From | Mingming Cao <> | Date | Wed, 22 Mar 2006 10:18:45 -0800 |
| |
On Wed, 2006-03-22 at 13:08 +0000, Alan Cox wrote: > 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. >
This is pretty much what ext3 block reservation does, every inode has a range of disk blocks(or call it extent) that are reserved (or call it preallocated).
> 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 > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Ext2-devel mailing list > Ext2-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ext2-devel
- 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/
| |