public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit]
Date: Wed, 22 Mar 2006 13:08:50 +0000	[thread overview]
Message-ID: <1143032930.3584.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20060322011034.GP12571@goober>

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


  parent reply	other threads:[~2006-03-22 13:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22  1:10 [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit] Valerie Henson
2006-03-22  8:40 ` Valerie Henson
2006-03-22 13:08 ` Alan Cox [this message]
2006-03-22 18:18   ` [Ext2-devel] " Mingming Cao
2006-03-22 18:16 ` [Ext2-devel] " Mingming Cao
     [not found]   ` <200603230011.53793.ioe-lkml@rameria.de>
2006-03-22 23:52     ` Mingming Cao
2006-03-22 19:09 ` Badari Pulavarty
2006-03-22 22:48   ` Valerie Henson
2006-03-23  1:55     ` Andrew Morton
2006-03-24 14:32       ` Valerie Henson
2006-03-24 15:35         ` Dave Kleikamp
2006-03-24 18:48         ` Andrew Morton
2006-03-24 19:13           ` Mingming Cao
2006-03-24 19:31             ` Andreas Dilger
2006-03-24 18:52         ` Theodore Ts'o
2006-03-24 19:14           ` Mingming Cao
2006-03-24 19:28         ` Andreas Dilger
2006-03-24 20:01           ` Theodore Ts'o
2006-03-24 21:00             ` Andreas Dilger
2006-03-24 21:39               ` Theodore Ts'o
2006-03-24 22:16                 ` Andreas Dilger
2006-03-25  5:13                   ` Suparna Bhattacharya
2006-03-25 17:38                   ` Ben Pfaff
2006-03-24 20:52           ` [Ext2-devel] " Matthew Wilcox
2006-03-24 21:23             ` Andreas Dilger

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=1143032930.3584.5.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@linux.intel.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=val_henson@linux.intel.com \
    --cc=zach.brown@oracle.com \
    /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