From: "Jose R. Santos" <jrs@us.ibm.com>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: block groups with no inode tables
Date: Tue, 10 Jul 2007 12:12:21 -0500 [thread overview]
Message-ID: <20070710121221.5478a1e3@rx8> (raw)
Hi folks,
As I play with the allocation of the metadata for the FLEX_BG feature,
it seems that we could benefit from having block groups with no inode
tables. Right now we allocate one inode table per bg base on the
inode_blocks_per_group. For FLEX_BG though, it would make more sense
to have a larger inode tables that fully use the inode bitmap allocated
on the first few block groups. Once we reach the number of inode per
FLEX_BG, then the remaining block groups could then have no inode
tables defined.
The idea here is that we better utilize the inode bitmaps and reduce the
number of inode tables to improve mkfs/fsck times. We could also
support expansion of inode since we have block groups that have empty
entries in the block group descriptors and as long as we can find
enough empty blocks for the inode table expanding the number of inodes
should be relatively easy.
Don't know if ext4 currently supports this. Any thoughts?
-JRS
next reply other threads:[~2007-07-10 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 17:12 Jose R. Santos [this message]
2007-07-10 17:30 ` block groups with no inode tables coly li
2007-07-10 17:40 ` Dave Kleikamp
2007-07-10 15:59 ` Mingming Cao
2007-07-10 19:09 ` Dave Kleikamp
2007-07-11 4:50 ` Andreas Dilger
2007-07-10 20:30 ` Theodore Tso
2007-07-11 4:31 ` 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=20070710121221.5478a1e3@rx8 \
--to=jrs@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).