On Tue, Sep 06, 2011 at 05:12:36PM +0200, Jan Kara wrote: > To verify reclaim behavior for VFS quotas, we could pull quota structures > in memory using GETQUOTA and then apply memory pressure to have them > reclaimed. If we also want to combine this with updates to those structures > because of allocations it gets more complicated. We'd have to do IO for > several different users in sequence under memory pressure so that all > inodes of one user get pushed out of memory and quota structure is thus > freed for reclaim as well. > > As for racing lookups / other quota operations - these are not that > much interesting for VFS quotas because > a) once quota structure is created, it's position on disk is fixed > b) any operation on quota file that does more than update accounting > information in a structure is protected by per quota-file mutex. > c) in memory operations with quota structures are protected by one global > spinlock It's fairly similar for XFS - but we still have code to e.g. retry the lookup after we did a memory allocation in both quota implementation. I just change the way the one in XFS worked, so I'm looking for a way to actually test that path. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
