From: Theodore Tso <tytso@mit.edu>
To: Alexandre Ratchov <alexandre.ratchov@bull.net>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-ext4@vger.kernel.org
Subject: Re: ext4 compat flag assignments
Date: Wed, 4 Oct 2006 16:04:40 -0400 [thread overview]
Message-ID: <20061004200440.GB1656@thunk.org> (raw)
In-Reply-To: <20060928085515.GC27104@openx1.frec.bull.fr>
On Thu, Sep 28, 2006 at 10:55:15AM +0200, Alexandre Ratchov wrote:
> struct ext4_super_block
> {
> /* at offset 0xfe */
> __le32 s_desc_size; /* Group descriptor size */
> /* at offset 0x150 */
> __le32 s_blocks_count_hi; /* Blocks count */
> __le32 s_r_blocks_count_hi; /* Reserved blocks count */
> __le32 s_free_blocks_count_hi; /* Free blocks count */
> __le32 s_jnl_blocks_hi[17]; /* Backup of the journal inode */
> };
Why do we need to have the high blocks # of the journal inode.
s_jnl_blocks was just a backup of the i_blocks[] array. But if we are
assuming that we will only support 64-bits using extents, we shouldn't
need s_jnl_blocks_hi[]. How specifically is this array being used in
the patches?
- Ted
next prev parent reply other threads:[~2006-10-04 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 9:15 ext4 compat flag assignments Andreas Dilger
2006-09-28 8:55 ` Alexandre Ratchov
2006-09-28 20:29 ` Andi Kleen
2006-09-28 22:41 ` Andreas Dilger
2006-09-28 23:06 ` Andi Kleen
2006-10-02 4:34 ` Andreas Dilger
2006-09-28 23:06 ` Andreas Dilger
2006-10-04 20:04 ` Theodore Tso [this message]
2006-10-05 0:19 ` Andreas Dilger
2006-10-05 2:02 ` Theodore Tso
2006-10-06 13:33 ` Valerie Clement
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=20061004200440.GB1656@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@clusterfs.com \
--cc=alexandre.ratchov@bull.net \
--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