From: Andrew Morton <akpm@osdl.org>
To: cmm@us.ibm.com
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 4/9] 48bit support in extents
Date: Wed, 9 Aug 2006 23:40:54 -0700 [thread overview]
Message-ID: <20060809234054.f9365c4b.akpm@osdl.org> (raw)
In-Reply-To: <1155172873.3161.83.camel@localhost.localdomain>
On Wed, 09 Aug 2006 18:21:13 -0700
Mingming Cao <cmm@us.ibm.com> wrote:
> +/* this macro combines low and hi parts of phys. blocknr into ext4_fsblk_t */
This isn't a macro.
> +static inline ext4_fsblk_t ext_pblock(struct ext4_extent *ex)
> +{
> + ext4_fsblk_t block;
> +
> + block = le32_to_cpu(ex->ee_start);
> + if (sizeof(ext4_fsblk_t) > 4)
> + block |= ((ext4_fsblk_t) le16_to_cpu(ex->ee_start_hi) << 31) << 1;
> + return block;
> +}
Oh. I see the other patch did
typedef sector_t ext4_fs_block_t;
(except someone misspelled "block" as "blk" ;))
Do we really want to do this? I guess there's some value, for people with
32-bit machines who want extents and who are too mean to use a 64-bit
sector_t. But gee that's marginal. And it introduces interesting
compatibility questions and significantly adds to the testing burden.
I think that requiring 64-bit sector_t is reasonable?
Then again, I see from the other patches that considerable thought and
effort has gone into sustaining this turkey, so I guess I'm missing
something again.
next prev parent reply other threads:[~2006-08-10 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 1:21 Mingming Cao
2006-08-10 6:40 ` Andrew Morton [this message]
2006-08-10 6:54 ` Jeff Garzik
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=20060809234054.f9365c4b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome