From: "Amit K. Arora" <aarora@linux.vnet.ibm.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: ext4-patch-queue rebased to 2.6.22
Date: Tue, 10 Jul 2007 23:25:58 +0530 [thread overview]
Message-ID: <20070710175558.GA15345@amitarora.in.ibm.com> (raw)
In-Reply-To: <20070710170939.GA6417@schatzie.adilger.int>
On Tue, Jul 10, 2007 at 11:09:39AM -0600, Andreas Dilger wrote:
> On Jul 10, 2007 20:24 +0530, Amit K. Arora wrote:
> > On Mon, Jul 09, 2007 at 01:37:56PM -0400, Theodore Ts'o wrote:
> > > So we're just waiting for Amit to make the minor on-disk format change
> > > Andreas suggested before we push to Linus.
> >
> > 2. Added a new patch ext4-fallocate-8-new-ondisk-format and updated
> > the series file. This patch, as suggested by Andreas, will allow
> > an initialized extent to be of max 2^15 length. Main purpose of this
> > change is to have a better extent-to-group alignment.
> > For uninitialized extents the max length remains same - i.e. 2^15 - 1.
>
> One tiny change I'd ask for in this patch (it isn't critical to get in
> before the upstream submission as it is only code style) is instead of
> using (EXT_MAX_LEN - 1) for uninitialized extents, instead use a separate
> #define EXT_UNINIT_MAX_LEN (EXT_MAX_LEN - 1) and use that in the code.
> While a minor change, this localizes the knowledge of the maximum length
> of uninitialized extents into just one place - right after the maximum
> length of initialized extents.
>
> It might even make sense to change the other #define to be called
> EXT_INIT_MAX_LEN so people have to think about this when using the #define.
Done. Changes are in ext4 patch queue.
Can you please have a quick look and see if this is what you preferred ?
--
Regards,
Amit Arora
next prev parent reply other threads:[~2007-07-10 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 17:37 ext4-patch-queue rebased to 2.6.22 Theodore Ts'o
2007-07-09 21:15 ` Mingming Cao
2007-07-10 14:54 ` Amit K. Arora
2007-07-10 17:09 ` Andreas Dilger
2007-07-10 17:55 ` Amit K. Arora [this message]
2007-07-10 20:26 ` 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=20070710175558.GA15345@amitarora.in.ibm.com \
--to=aarora@linux.vnet.ibm.com \
--cc=adilger@clusterfs.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 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).