public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH, E2FSPROGS] On-disk format for inode extra size control inode size
Date: Wed, 18 Oct 2006 13:34:38 -0600	[thread overview]
Message-ID: <20061018193437.GG3509@schatzie.adilger.int> (raw)
In-Reply-To: <E1Ga4rR-000534-CE@candygram.thunk.org>

On Oct 18, 2006  02:25 -0400, Theodore Ts'o wrote:
> On-disk format for controlling the inode size
> 
> - EXT4_FEATURE_RO_COMPAT_EXTRA_ISIZE (0x0040?) - add s_min_extra_isize and
>   s_want_extra_isize fields to superblock, which allow specifying
>   the minimum and desired i_extra_isize fields in large inodes
>   (for nsec+epoch timestamps, potential other uses).  Needs RO_COMPAT
>   flag handling, needs e2fsck support, patch complete, little testing.
> 
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

> @@ -405,6 +405,11 @@
>  	} osd2;				/* OS dependent 2 */
>  	__u16	i_extra_isize;
>  	__u16	i_pad1;
> +	__u32	i_ctime_extra;	/* extra Change time (nsec << 2 | epoch) */

There was some discussion about moving the i_ctime_extra field into the
small inode, for use as a version field by NFSV4.  The proposed field was
l_i_reserved2 in the original Bull patch.

> +	__u32	i_mtime_extra;	/* extra Mod. time (nsec << 2 | epoch) */
                                         ^^^ Modify

Looks good otherwise.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

  reply	other threads:[~2006-10-18 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18  6:25 [PATCH, E2FSPROGS] On-disk format for inode extra size control inode size Theodore Ts'o
2006-10-18 19:34 ` Andreas Dilger [this message]
2006-10-18 22:16   ` Theodore Tso
2006-10-18 22:59     ` 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=20061018193437.GG3509@schatzie.adilger.int \
    --to=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