From: "Jose R. Santos" <jrs@us.ibm.com>
To: cmm@us.ibm.com
Cc: Laurent Vivier <Laurent.Vivier@bull.net>,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
Andreas Dilger <adilger@clusterfs.com>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [RFC][PATCH] Set JBD2_FEATURE_INCOMPAT_64BIT on filesystems larger than 32-bit blocks (take 2).
Date: Tue, 5 Jun 2007 14:58:14 -0500 [thread overview]
Message-ID: <20070605145814.2e9677f7@gara> (raw)
In-Reply-To: <1181065603.3839.8.camel@dyn9047017103.beaverton.ibm.com>
On Tue, 05 Jun 2007 10:46:43 -0700
Mingming Cao <cmm@us.ibm.com> wrote:
> The better choice to me is using ext4_blocks_count() to hide the details
> of the little endian. It's fine to use s_blocks_count_hi directly, just
> to make it clear, this is on-disk superblock data and better to do
> little endian conversion like read-in other on-disk superblock fields.
On the grounds of avoiding confusion regarthing the use of
s_blocks_count_hi, I agree that using ext4_blocks_count() is the right
thing to do. I will resubmit the patch and also eliminate the the 4
lines of comments since the code would be more explicit as to what its
doing.
> Yeah, it probably unnecessary in this case, but I don't think the extra
> instruction plays an important role in the performance, (this is only
> called at mount time, and there are lots of other places doing little
> endian conversion in ext4_fill_super() anyway).
I originally wrote this patch using ext4_blocks_count() but later
changed it since it was faster to do it this way. While mounting is
not always a performance critical section, I still see those few extra
instructions a little wasteful. :)
-JRS
prev parent reply other threads:[~2007-06-05 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 15:52 [RFC][PATCH] Set JBD2_FEATURE_INCOMPAT_64BIT on filesystems larger than 32-bit blocks Jose R. Santos
2007-06-01 22:54 ` Andreas Dilger
2007-06-04 16:32 ` [RFC][PATCH] Set JBD2_FEATURE_INCOMPAT_64BIT on filesystems larger than 32-bit blocks (take 2) Jose R. Santos
2007-06-04 17:57 ` Andreas Dilger
2007-06-04 23:01 ` Mingming Cao
2007-06-04 23:32 ` Andreas Dilger
2007-06-05 11:41 ` Jose R. Santos
2007-06-05 13:14 ` Dave Kleikamp
2007-06-05 13:26 ` Laurent Vivier
2007-06-05 13:49 ` Jose R. Santos
2007-06-05 14:03 ` Laurent Vivier
2007-06-05 15:46 ` Jose R. Santos
2007-06-05 16:07 ` Laurent Vivier
2007-06-05 17:46 ` Mingming Cao
2007-06-05 19:58 ` Jose R. Santos [this message]
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=20070605145814.2e9677f7@gara \
--to=jrs@us.ibm.com \
--cc=Laurent.Vivier@bull.net \
--cc=adilger@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.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