From: Andreas Dilger <adilger@clusterfs.com>
To: Alexandre Ratchov <alexandre.ratchov@bull.net>
Cc: Mingming Cao <cmm@us.ibm.com>,
akpm@osdl.org, shaggy@us.ibm.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Updated ext4 patches for 2.6.18-rc6
Date: Fri, 8 Sep 2006 12:09:32 -0600 [thread overview]
Message-ID: <20060908180931.GK6441@schatzie.adilger.int> (raw)
In-Reply-To: <20060908161324.GA19256@openx1.frec.bull.fr>
On Sep 08, 2006 18:13 +0200, Alexandre Ratchov wrote:
> there are 2 more patches:
>
> * ext4_remove_relative_block_numbers:
>
> use 48bit absolute block numbers instead of mixed relative/absolute block
> numbers. This is simpler and seems to fix issues with large file systems.
>
> * ext4_allow_larger_descriptor_size:
>
> allow larger block group descriptors: this patch will allow to add new
> features that need more space in the block descriptor.
Hmm, I'm a bit confused. If we are adding larger block group descriptors,
why wouldn't we put 32-bit "high" block numbers into the larger descriptor
space? That could be part of the INCOMPAT_64BIT support.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2006-09-08 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 4:11 [RFC][1/4] ext2/3/4: enlarge blocksize sho
2006-09-08 7:01 ` Updated ext4 patches for 2.6.18-rc6 Mingming Cao
2006-09-08 16:13 ` Alexandre Ratchov
2006-09-08 16:15 ` [patch 1/2] " Alexandre Ratchov
2006-09-08 16:18 ` [patch 2/2] " Alexandre Ratchov
2006-09-08 18:09 ` Andreas Dilger [this message]
2007-06-21 22:34 ` [RFC][1/4] ext2/3/4: enlarge blocksize Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2006-09-08 10:17 Updated ext4 patches for 2.6.18-rc6 sho
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=20060908180931.GK6441@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=alexandre.ratchov@bull.net \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@us.ibm.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