linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Kalpak Shah <kalpak@clusterfs.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>,
	Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
	Eric Sandeen <sandeen@redhat.com>, sct <sct@redhat.com>,
	TheodoreTso <tytso@mit.edu>
Subject: Re: [PATCH 1/1] [RFC] 64-bit inode version
Date: Wed, 11 Apr 2007 12:30:04 -0600	[thread overview]
Message-ID: <20070411183004.GU5967@schatzie.adilger.int> (raw)
In-Reply-To: <1176297438.7350.23.camel@garfield>

On Apr 11, 2007  18:47 +0530, Kalpak Shah wrote:
> This patch adds 64-bit inode version support to ext4. The lower 32 bits
> are stored in the osd1.linux1.l_i_version field while the high 32 bits
> are stored in the i_version_hi field newly created in the ext4_inode.

Note that this is NOT a duplicate of the Bull "change attribute" patches,
rather this implements only the on-disk storage of the 64-bit version
number, and the ability to resize i_extra_isize to allow inodes in the
filesystem which weren't created with a big enough i_extra_isize to add
new fields.  That would basically be needed by all ext4 filesystems that
did not yet have the nanosecond timestamp patches applied when they were
created.

> +		if (EXT4_FITS_IN_INODE(raw_inode, ei, i_version_hi))
> +			ei->i_fs_version |= (__u64)(le32_to_cpu(raw_inode->i_version_hi))
> +									 << 32;

Minor nit - can the wrapping here be fixed when it is added to the git tree:

			ei->i_fs_version |=
				(__u64)le32_to_cpu(raw_inode->i_version_hi)<<32;

> +		if (EXT4_FITS_IN_INODE(raw_inode, ei, i_version_hi)) {
> +			raw_inode->i_version_hi = cpu_to_le32(ei->i_fs_version
> +									>> 32);

And here:
			raw_inode->i_version_hi =
				cpu_to_le32(ei->i_fs_version >> 32);


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

  reply	other threads:[~2007-04-11 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11 13:17 [PATCH 1/1] [RFC] 64-bit inode version Kalpak Shah
2007-04-11 18:30 ` Andreas Dilger [this message]
2007-05-16  1:15 ` Mingming Cao
2007-05-16  8:22   ` Kalpak Shah

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=20070411183004.GU5967@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=kalpak@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=sct@redhat.com \
    --cc=shaggy@linux.vnet.ibm.com \
    --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).