Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+6\/7\]\s+XFS\:\s+Combine\s+the\s+XFS\s+and\s+Linux\s+inodes\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+6\/7\]\s+XFS\:\s+Combine\s+the\s+XFS\s+and\s+Linux\s+inodes\.\s*$/: 9 ]

Total 9 documents matching your query.

1. [PATCH 6/7] XFS: Combine the XFS and Linux inodes. (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 14 Aug 2008 17:14:42 +1000; To avoid issues with different lifecycles of XFS and Linux inodes, embedd the linux inode inside the XFS inode. This means that the linux inode has the same lifecycle as the XFS inode, even when it h; /archives/xfs/2008-08/msg00248.html (33,238 bytes)
2. Re: [PATCH 6/7] XFS: Combine the XFS and Linux inodes. (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Thu, 14 Aug 2008 16:00:06 -0400; Actually we can just do this unconditionally, as the atime values don't become invalid just because the VFS doesn't know about the inode anymore. And two useless because already previously updated a; /archives/xfs/2008-08/msg00257.html (12,595 bytes)
3. Re: [PATCH 6/7] XFS: Combine the XFS and Linux inodes. (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 18 Aug 2008 10:34:51 +1000; Ok, I'll make it unconditional. Yup, I thought I caught all of them :/ Ah, separate patch not sent. basically does: void inode_used(struct super_block *sb, struct inode *inode) { spin_lock(&inode_loc; /archives/xfs/2008-08/msg00285.html (14,149 bytes)
4. [PATCH 6/7] XFS: Combine the XFS and Linux inodes. (score: 1): Author: xx>; Date: Thu, 14 Aug 2008 17:14:42 +1000; To avoid issues with different lifecycles of XFS and Linux inodes, embedd the linux inode inside the XFS inode. This means that the linux inode has the same lifecycle as the XFS inode, even when it h; /archives/xfs/2008-08/msg00696.html (33,238 bytes)
5. Re: [PATCH 6/7] XFS: Combine the XFS and Linux inodes. (score: 1): Author: xx>; Date: Thu, 14 Aug 2008 16:00:06 -0400; Actually we can just do this unconditionally, as the atime values don't become invalid just because the VFS doesn't know about the inode anymore. And two useless because already previously updated a; /archives/xfs/2008-08/msg00705.html (12,595 bytes)
6. Re: [PATCH 6/7] XFS: Combine the XFS and Linux inodes. (score: 1): Author: xx>; Date: Mon, 18 Aug 2008 10:34:51 +1000; Ok, I'll make it unconditional. Yup, I thought I caught all of them :/ Ah, separate patch not sent. basically does: void inode_used(struct super_block *sb, struct inode *inode) { spin_lock(&inode_loc; /archives/xfs/2008-08/msg00733.html (14,149 bytes)
7. [PATCH 6/7] XFS: Combine the XFS and Linux inodes. (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 14 Aug 2008 17:14:42 +1000; To avoid issues with different lifecycles of XFS and Linux inodes, embedd the linux inode inside the XFS inode. This means that the linux inode has the same lifecycle as the XFS inode, even when it h; /archives/xfs/2008-08/msg01144.html (33,332 bytes)
8. Re: [PATCH 6/7] XFS: Combine the XFS and Linux inodes. (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Thu, 14 Aug 2008 16:00:06 -0400; Actually we can just do this unconditionally, as the atime values don't become invalid just because the VFS doesn't know about the inode anymore. And two useless because already previously updated a; /archives/xfs/2008-08/msg01153.html (12,736 bytes)
9. Re: [PATCH 6/7] XFS: Combine the XFS and Linux inodes. (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 18 Aug 2008 10:34:51 +1000; Ok, I'll make it unconditional. Yup, I thought I caught all of them :/ Ah, separate patch not sent. basically does: void inode_used(struct super_block *sb, struct inode *inode) { spin_lock(&inode_loc; /archives/xfs/2008-08/msg01181.html (14,303 bytes)

Current List: 1 - 9
Page: [1]