public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Ratchov <alexandre.ratchov@bull.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Alexandre Ratchov <alexandre.ratchov@bull.net>,
	linux-ext4@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: rfc: [patch] change attribute for ext3
Date: Wed, 13 Sep 2006 20:30:01 +0200	[thread overview]
Message-ID: <20060913183001.GA1702@moule.localdomain> (raw)
In-Reply-To: <1158171071.6072.10.camel@lade.trondhjem.org>

On Wed, Sep 13, 2006 at 02:11:11PM -0400, Trond Myklebust wrote:
> On Wed, 2006-09-13 at 18:42 +0200, Alexandre Ratchov wrote:
> > hello, 
> > 
> > here is a small patch that adds the "change attribute" for ext3
> > file-systems;
> > 
> > the change attribute is a simple counter that is reset to zero on
> > inode creation and that is incremented every time the inode data is
> > modified (similarly to the "ctime" time-stamp).
> 
> I would really have preferred a full-blown 64-bit counter as per
> RFC3530, but I suppose we could always combine this change attribute
> with the high word from ctime in order to make up the NFSv4 change
> attribute. That should keep us safe until someone develops a ramdisk
> with < 1 nsecond access time.
> 

do you mean something like "(ctime.tv_sec << 32) | change_attribute"? this
would allow 2^32 inode changes per second.

For ext3 it's hard to find unused bits in the on-disk inode structure, but
ext4 inode may become larger in the future, allowing a 64bit counter.

-- Alexandre

  reply	other threads:[~2006-09-13 18:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 16:42 rfc: [patch] change attribute for ext3 Alexandre Ratchov
2006-09-13 18:11 ` Trond Myklebust
2006-09-13 18:30   ` Alexandre Ratchov [this message]
2006-09-13 19:06     ` Trond Myklebust
2006-09-13 20:31       ` Randy.Dunlap
2006-09-14  9:23     ` Andreas Dilger
2006-09-14 13:48       ` Alexandre Ratchov
2006-11-14 22:17       ` Andreas Dilger
2006-11-24  0:23         ` Andreas Dilger
2006-11-28 19:00           ` J. Bruce Fields
2006-11-28 22:06             ` Andreas Dilger
2006-09-14 13:46   ` Peter Staubach
2006-09-14 13:56     ` Trond Myklebust
2006-09-14 14:06     ` Alexandre Ratchov
2006-12-14  1:24   ` Andreas Dilger
2006-12-14  1:52     ` J. Bruce Fields
2006-12-14 16:48       ` Trond Myklebust
2006-12-14 23:04         ` Andreas Dilger
2006-09-13 19:31 ` Andreas Dilger
2006-09-14  1:24   ` J. Bruce Fields
2006-09-14 13:21   ` Alexandre Ratchov
2006-09-14 21:01     ` Andreas Dilger
2006-09-15 10:19       ` Alexandre Ratchov
2006-09-15 16:18         ` Andreas Dilger
2006-11-29 18:54 ` [RFC] [patch 0/3] change attribute for ext4 Jean-Noel Cordenner

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=20060913183001.GA1702@moule.localdomain \
    --to=alexandre.ratchov@bull.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    --cc=trond.myklebust@fys.uio.no \
    /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