All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: "Jose R. Santos" <jrs@us.ibm.com>,
	Andreas Dilger <adilger@clusterfs.com>,
	linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [RFC] BIG_BG vs extended META_BG in ext4
Date: Mon, 02 Jul 2007 10:12:57 -0400	[thread overview]
Message-ID: <1183385577.3864.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20070702154939.GC4720@thunk.org>

On Mon, 2007-07-02 at 11:49 -0400, Theodore Tso wrote:
> On Sun, Jul 01, 2007 at 09:48:33AM -0500, Jose R. Santos wrote:
> > Is your concern due to being unable to find contiguous block in the
> > case that a bad disk area is in one of the bitmap blocks?  One thing we
> > can do is try to search for another set of contiguous blocks and if we
> > fail to find one, we can flag the block group and move to an indirect
> > block approach to allocating the bitmaps.  At this point, we do lose
> > some of the performance benefits of BIG_BG, but we would still be able
> > to use the block group.
> 
> Yes, my concern is what we might need to do if for some reason e2fsck
> needs to reallocate the bitmap blocks.  I don't think an indirect
> block scheme is the right approach, though; we're adding a lot of
> complexity for a case that probably wouldn't be used but very, very
> rarely.
> 
> My proposal (as we discsused) in the call, is to implement BIG_BG as
> meaning the following:
> 
> 	1) Implementations must understand and use the s_desc_size
> 	superblock field to determine whether block group descriptors
> 	are the old 32 bytes or the newer 64 bytes format.  
> 	
> 	2) Implementations must support the newer ext4_group_desc
> 	format in particular to support bg_free_blocks_count_hi and
> 	bg_free_inodes_count_hi
> 
> 	3) Implementations will relax constraints on where the
> 	superblock, bitmaps, and inode tables for a particular block
> 	group will be stored.
>

I agree.

> So with that, we can experiment with what size block groups really
> make sense, versus using the extended metablockgroup idea, or possibly
> doing both.
> 

How about incorporating some of the chunkfs ideas into this BIG_BG or
extended metablockgroups? The original block group size (128MB) is
probably too small that would results in many continous inodes. By
enlarging the size of groups via BIG_BG or extended metablockgroups, we
could add dirty/clean bit to allow partical/parallel fsck, and something
like that. Any thoughts on thhis?


Mingming

  reply	other threads:[~2007-07-02 17:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29 22:09 [RFC] BIG_BG vs extended META_BG in ext4 Jose R. Santos
2007-06-30  5:51 ` Andreas Dilger
2007-06-30 14:24   ` Mingming Cao
2007-07-01  4:39   ` Jose R. Santos
2007-07-01 12:30     ` Theodore Tso
2007-07-01 14:48       ` Jose R. Santos
2007-07-02 15:49         ` Theodore Tso
2007-07-02 14:12           ` Mingming Cao [this message]
2007-07-05  6:56             ` Valerie Henson
     [not found] ` <D5D3223C-4EB0-413B-A81A-05F6DDC0FEEB@bull.net>
2007-07-01  4:40   ` Jose R. Santos
2007-07-01 16:31     ` Andreas Dilger
2007-07-02 14:39       ` Jose R. Santos
2007-07-03 17:55         ` 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=1183385577.3864.7.camel@localhost.localdomain \
    --to=cmm@us.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=jrs@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.