Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+1\/4\]\s+xfs\:\s+reclaim\s+inodes\s+under\s+a\s+write\s+lock\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+1\/4\]\s+xfs\:\s+reclaim\s+inodes\s+under\s+a\s+write\s+lock\s*$/: 2 ]

Total 2 documents matching your query.

1. [PATCH 1/4] xfs: reclaim inodes under a write lock (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 11 Jan 2010 10:51:45 +1100; Make the inode tree reclaim walk exclusive to avoid races with concurrent sync walkers and lookups. This is a version of a patch posted by Christoph Hellwig that avoids all the code duplication. Sign; /archives/xfs/2010-01/msg00137.html (18,848 bytes)
2. Re: [PATCH 1/4] xfs: reclaim inodes under a write lock (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Mon, 11 Jan 2010 05:18:36 -0500; looks good, Reviewed-by: Christoph Hellwig <hch@xxxxxx> FYI: I would rename xfs_reclaim_inode_now to just xfs_reclaim_inode, but unless Alex wants to edit it let's just get the patch in for now.; /archives/xfs/2010-01/msg00141.html (9,116 bytes)

Current List: 1 - 2
Page: [1]