Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\,\s+needs\s+new\s+owner\]\s+xfs

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\,\s+needs\s+new\s+owner\]\s+xfs_repair\s+memory\s+optimization\s*$/: 3 ]

Total 3 documents matching your query.

1. [PATCH, needs new owner] xfs_repair memory optimization (score: 1): Author: Mark Goodwin <markgw@xxxxxxx>; Date: Fri, 23 Jan 2009 13:09:32 +1100; A known limitation of xfs_repair is the large amount of memory it requires, depending on filesystem size and number of inodes, etc. The attached patch series, originally by Barry Bnaujok, is close to; /archives/xfs/2009-01/msg01067.html (7,299 bytes)
2. Re: [PATCH, needs new owner] xfs_repair memory optimization (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Sat, 24 Jan 2009 09:23:31 -0500; I did a quick look over it on the plane today and it looks quite nice to me. I guess there are no patch descriptions left anywhere? Otherwise some of the patch might need some minor polishing, e.g. t; /archives/xfs/2009-01/msg01093.html (8,167 bytes)
3. Re: [PATCH, needs new owner] xfs_repair memory optimization (score: 1): Author: Mark Goodwin <markgw@xxxxxxx>; Date: Sun, 25 Jan 2009 11:03:19 +1100; The attached patch series, originally by Barry Bnaujok, is close to being finished but requires a new owner to do some final testing and polishing. It applies cleanly against top-of-tree xfsprogs-3.0; /archives/xfs/2009-01/msg01099.html (10,559 bytes)

Current List: 1 - 3
Page: [1]