Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+xfs\:\s+remove\s+lazy\s+per\-AG\s+initialization\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+xfs\:\s+remove\s+lazy\s+per\-AG\s+initialization\s*$/: 4 ]

Total 4 documents matching your query.

1. [PATCH] xfs: remove lazy per-AG initialization (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Fri, 28 May 2010 13:51:08 -0400; Historically XFS initializes the allocator / inode allocator per-AG lazily, that is the first time this information is required. For filesystems that use lazy superblock counters (which is the defaul; /archives/xfs/2010-05/msg00465.html (35,024 bytes)
2. Re: [PATCH] xfs: remove lazy per-AG initialization (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 31 May 2010 09:09:15 +1000; Which is not common, so isn't frequently triggered in the normal mount process. The reason for the lazy initialisation is to speed the mount process up when there are thousands of AGs. That is, we av; /archives/xfs/2010-05/msg00478.html (8,389 bytes)
3. Re: [PATCH] xfs: remove lazy per-AG initialization (score: 1): Author: Alex Elder <aelder@xxxxxxx>; Date: Thu, 03 Jun 2010 16:58:10 -0500; It's interesting that the time penalty you're talking about doesn't go away, it just becomes less noticeable because it's aggregated over subsequent access to the AG's. I like the cleanup too, but I; /archives/xfs/2010-06/msg00033.html (9,076 bytes)
4. Re: [PATCH] xfs: remove lazy per-AG initialization (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Fri, 4 Jun 2010 11:42:29 +1000; Right, the penalty is currently taken at access time, rather than at mount time. One way to test the impact is to compare the runtime difference for xfstests with MKFS_OPTIONS="-d agsize=16m" to bump; /archives/xfs/2010-06/msg00045.html (9,005 bytes)

Current List: 1 - 4
Page: [1]