Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\/2\]\s+xfs_export_operations\.commit_metadata\s*$/: 13 ]

Total 13 documents matching your query.

1. [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Ben Myers <bpm@xxxxxxx>
Date: Thu, 11 Feb 2010 13:26:22 -0600
This is the commit_metadata export operation for XFS, including the changes suggested by hch and dgc: - Takes two two inodes instead of dentries and can assume the parent is always set. - Uses xfs_lo
/archives/xfs/2010-02/msg00170.html (10,231 bytes)

2. [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Ben Myers <bpm@xxxxxxx>
Date: Thu, 11 Feb 2010 16:05:05 -0600
This is the commit_metadata export operation for XFS, including the changes suggested by hch and dgc: - Takes two two inodes instead of dentries and can assume the parent is always set. - Uses xfs_lo
/archives/xfs/2010-02/msg00174.html (9,913 bytes)

3. Re: [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Alex Elder <aelder@xxxxxxx>
Date: Fri, 12 Feb 2010 08:46:46 -0600
I alluded to this in my review of the first patch. This could be changed considered in a more generic sense, "sync one or two inodes' metadata" rather than presupposing the two inodes have a parent/c
/archives/xfs/2010-02/msg00178.html (12,808 bytes)

4. Re: [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 12 Feb 2010 12:47:07 -0500
Or just implement my later suggestion to only pass one inode to the method and cal in on both inodes. For the non-create case where we have only one transaction to deal with fhr first call will take
/archives/xfs/2010-02/msg00188.html (11,714 bytes)

5. Re: [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: bpm@xxxxxxx
Date: Fri, 12 Feb 2010 13:56:47 -0600
I chose not implement that suggestion because I prefer not to rely upon the coincidence that the child be modified last and synced first in knfsd. It is better that the intent of the patch be clear,
/archives/xfs/2010-02/msg00191.html (12,551 bytes)

6. Re: [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
Date: Fri, 12 Feb 2010 15:03:59 -0500
Assuming the xfs tree's something stable, I could also just go ahead and pull it into the nfsd tree. (Or we could do it the other way around--as long as when the merge window opens we try to send the
/archives/xfs/2010-02/msg00193.html (10,326 bytes)

7. Re: [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 12 Feb 2010 15:35:59 -0500
It does ot rely on that coincidence for correctness, just for a small performance optimization. The order of parent and child only happens in the create case where NFS does a separate ->setattr call.
/archives/xfs/2010-02/msg00197.html (11,332 bytes)

8. Re: [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 12 Feb 2010 15:37:01 -0500
The xfs tree is supposed to be stable and we only had very few incidents where a patch had to be pulled again. But it's also a quite large set of changes.
/archives/xfs/2010-02/msg00198.html (10,200 bytes)

9. [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Ben Myers <bpm@xxxxxxx>
Date: Tue, 16 Feb 2010 15:04:18 -0600
This is the commit_metadata export operation for XFS. - Takes one inode to be committed. - Forces the log up to the lsn of the inode. - Doesn't force the log if the inode doesn't have a pincount. Sig
/archives/xfs/2010-02/msg00265.html (9,585 bytes)

10. Re: [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 16 Feb 2010 17:07:48 -0500
Looks good, Reviewed-by: Christoph Hellwig <hch@xxxxxx>
/archives/xfs/2010-02/msg00269.html (7,606 bytes)

11. Re: [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 17 Feb 2010 11:29:43 +1100
That could be simplified to: if (xfs_ipincount(ip)) _xfs_log_force(mp, ip->i_itemp->ili_last_lsn XFS_LOG_FORCE | XFS_LOG_SYNC, NULL); Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
/archives/xfs/2010-02/msg00270.html (10,601 bytes)

12. [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Ben Myers <bpm@xxxxxxx>
Date: Wed, 17 Feb 2010 14:05:16 -0600
This is the commit_metadata export operation for XFS. - Takes one inode to be committed. - Forces the log up to the lsn of the inode. - Doesn't force the log if the inode doesn't have a pincount. Sig
/archives/xfs/2010-02/msg00295.html (9,321 bytes)

13. Re: [PATCH 2/2] xfs_export_operations.commit_metadata (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 18 Feb 2010 10:05:44 +1100
Looks good, Ben. Reviewed-by: Dave Chinner <david@xxxxxxxxxxxxx> -- Dave Chinner david@xxxxxxxxxxxxx
/archives/xfs/2010-02/msg00303.html (8,417 bytes)


This search system is powered by Namazu