Re: [PATCH 1/2] i_version update - vfs part

Hi, Here you can find some performance comparison in terms of CPU utilization and transactions per second (using FFSB) on ext4 filesystem with and without i_version option. http://bullopensource.org/ext4/20071116/ffsb-write.html regards, Jean noel - To unsubscribe from this list: send the li

[patch] i_version mount option

hi, This patch apply on the top of the ext4 git tree. It adds a mount option to enable i_version feature for ext4. Signed-off-by: Jean noel Cordenner <[EMAIL PROTECTED]> Index: linux-2.6.22-ext4/fs/ext4/super.c === ---

Re: Performance testing results

Valerie Clement a écrit : Hi, I re-ran some FFSB tests on ext3, ext4 and xfs filesystems, on a 2.6.22-rc5 kernel and with the latest ext4-git-tree (update of June 26). The results are available here: http://www.bullopensource.org/ext4/20070627/ffsb-write.html Regards, Valérie An update of

Re: [PATCH 0/6] inode version updated patches

Mingming Cao a écrit : On Thu, 2007-06-14 at 21:26 +0530, Kalpak Shah wrote: Hi, I have updated the inode version patches and below are the details: 64-bit-i_version.patch which only replaces the 32-bit i_version field in the generic inode with a 64-bit i_version field. The VFS-level updates o

[patch 2/2] i_version update - ext4 part

:12:37.0 +0200 +++ linux-2.6.22-rc2-ext4-1/fs/ext4/xattr.h 2007-05-25 17:12:41.0 +0200 @@ -74,6 +74,9 @@ extern void ext4_xattr_delete_inode(handle_t *, struct inode *); extern void ext4_xattr_put_super(struct super_block *); +int ext4_expand_extra_isize(struct inode *inode, int new

[patch 1/2] i_version update - vfs part

rmay return the object's time_metadata attribute for this attribute's value but only if the filesystem object can not be updated more frequently than the resolution of time_metadata." Signed-off-by: Jean Noel Cordenner <[EMAIL PRO

[patch 0/2] i_version update

Hi, This is an update of the i_version patch. The i_version field is a 64bit counter that is set on every inode creation and that is incremented every time the inode data is modified (similarly to the "ctime" time-stamp). The aim is to fulfill a NFSv4 requirement for rfc3530: "5.5. Mandatory Att

[RFC] [patch 3/3] change attribute for ext4: user interface

This patch adds a ``st_change_attribute'' field in the stat structure, and modifies the stat(2) syscall accordingly. Currently the change is only visible on i386 and x86_64 archs. Signed-off-by: Celine Bourde Signed-off-by: Alexandre Ratchov Signed-off-by: Jean Noel Cordenn

[RFC] [patch 2/3] change attribute for ext4: ext4 specific code

This part of the patch concerns the ext4 code. Signed-off-by: Celine Bourde Signed-off-by: Alexandre Ratchov Signed-off-by: Jean Noel Cordenner <[EMAIL PROTECTED]> --- linux-2.6.19-rc2-mm2-CA.orig/fs/ext4/ialloc.c 2006-11-09 17:20:57.0 +0100 +++ linux-2.6.19-rc2-mm2

[RFC] [patch 1/3] change attribute for ext4: change attribute in the VFS

This part of the patch concerns the change attribute in the VFS layer. The definition of the change_attribute field in the inode and its update. Signed-off-by: Celine Bourde Signed-off-by: Alexandre Ratchov Signed-off-by: Jean Noel Cordenner <[EMAIL PROTECTED]> Index: linux-2.6.19-r

[RFC] [patch 0/3] change attribute for ext4

Hello, I've updated the change attribute patch for ext4 that was initially posted by Alexandre Ratchov. The change attribute is a simple counter that is set on inode creation and that is incremented every time the inode data is modified (similarly to the "ctime" time-stamp) and never reset.