Messages in this thread | | | Subject | Re: What's in ocfs2.git | From | Steven Whitehouse <> | Date | Mon, 04 Dec 2006 10:54:53 +0000 |
| |
Hi,
On Sun, 2006-12-03 at 12:31 -0800, Mark Fasheh wrote: > This e-mail describes the OCFS2 patches which I intend to push > upstream to Linus for 2.6.20. > > * Atime updates - thanks to Tiger Yang <tiger.yang@oracle.com>, ocfs2 now > writes to the inode atime field. This doesn't require any disk changes, > and is completely backwards compatible with older ocfs2 versions. An > inodes Atime is only updated if it hasn't changed within a certain > quantum. The user can define their own value at mount time, with 0 > indicating that atime should always be updated. This is very similar to > the scheme implemented by gfs2. In the future, I'd like to see a "relative > atime" mode, which functions in the manner described by Valerie Henson at: > > http://lkml.org/lkml/2006/8/25/380 > I'd like to second that. [adding Val Henson to the "to"] What (if anything) remains to be done before the relative atime patch is ready to go upstream? I'm happy to help out here if required,
Steve.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |