From: Theodore Tso <tytso@mit.edu>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Initial results of FLEX_BG feature.
Date: Wed, 11 Jul 2007 18:09:46 -0400 [thread overview]
Message-ID: <20070711220945.GG19456@thunk.org> (raw)
In-Reply-To: <20070711003004.531c9307@naruto>
On Wed, Jul 11, 2007 at 12:30:04AM -0500, Jose R. Santos wrote:
> > i think in the spirit of the original META_BG option, Ted had wanted to
> > put all the bitmaps from EXT4_DESC_PER_BLOCK groups somewhere within the
> > metagroup. It would also be interesting to see if moving ALL of the
> > group metadata to a single location in the filesystem makes a bit difference.
> > If not, then we may as well keep it spread out for safety.
My original intention was that META_BG would place the bitmaps and
inode tables at the beginning of each metagroup by default, but that
the constraints about where to put the bitmaps and inode tables would
be completely relaxed from the point of view of requirements by the
kernel and e2fsck. Unfortunately while I had patches which removed
the constraints checking, they never made it into mainline of either
the kernel or e2fsprogs, sigh.
- Ted
next prev parent reply other threads:[~2007-07-11 22:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 16:23 Initial results of FLEX_BG feature Jose R. Santos
2007-07-11 4:12 ` Andreas Dilger
2007-07-11 5:30 ` Jose R. Santos
2007-07-11 5:39 ` Eric Sandeen
2007-07-11 12:41 ` Andreas Dilger
2007-07-11 22:09 ` Theodore Tso [this message]
2007-07-11 22:14 ` Theodore Tso
2007-07-12 15:02 ` Jose R. Santos
2007-07-12 15:09 ` Jose R. Santos
2007-07-16 6:34 ` Andreas Dilger
2007-07-16 12:27 ` Jose R. Santos
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=20070711220945.GG19456@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@clusterfs.com \
--cc=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).