Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+setting\s+custom\s+extent\s+size\:\s+real\-time\s+section\s+only\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+setting\s+custom\s+extent\s+size\:\s+real\-time\s+section\s+only\?\s*$/: 24 ]

Total 24 documents matching your query.

21. Re: XFS setting custom extent size: real-time section only? (score: 1): Author: Heilige Gheist <hgheist@xxxxxxxxx>; Date: Tue, 25 Jul 2006 11:08:07 -0700 (PDT); [..] The application is reading and writing sparse file of 0.5-1GB, with heavy skew toward read. The data is written in clusters of various size, depending on data stream type. The filesystem is cons; /archives/xfs/2006-07/msg01091.html (9,928 bytes)
22. Re: XFS setting custom extent size: real-time section only? (score: 1): Author: Nathan Scott <nathans@xxxxxxx>; Date: Wed, 26 Jul 2006 09:00:51 +1000; Hmm. Yes, thats the one. No, but it does the best it can under the circumstances, which is usually pretty good. But its not really "extra" if you know you're going to use it, right? Its a different c; /archives/xfs/2006-07/msg01095.html (10,706 bytes)
23. Re: XFS setting custom extent size: real-time section only? (score: 1): Author: Heilige Gheist <hgheist@xxxxxxxxx>; Date: Mon, 31 Jul 2006 05:38:37 -0700 (PDT); [..] I think that I'll go for the custom extent size as the harder guarantee against fragmentation. It also looks to me that custom extent is easier for application to implement. Are there any other; /archives/xfs/2006-07/msg01162.html (10,487 bytes)
24. Re: XFS setting custom extent size: real-time section only? (score: 1): Author: Nathan Scott <nathans@xxxxxxx>; Date: Tue, 1 Aug 2006 08:29:54 +1000; Not really... only things like "its not there in old kernels", and "its not seen the level of testing and exposure of other XFS features, like preallocation", etc. Oh, I see. You don't need to estima; /archives/xfs/2006-07/msg01167.html (10,678 bytes)

Current List: 21 - 24
Page: [1] [2]