[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 05 Nov 2007 11:37:50 -0600
From: Eric Sandeen <sandeen@...hat.com>
To: Alex Tomas <bzzz.tomas@...il.com>
CC: Andreas Dilger <adilger@....COM>,
ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: delalloc fragmenting files?
Alex Tomas wrote:
> thanks for the data. the attached patch should fix couple issues:
> broken history output and policy in that smaller usable chunk to
> be used. can you give it a spin, please?
Hi Alex -
This looks *much* better:
First block: 100355
Last block: 2342657
Discontinuity: Block 30208 is at 133120 (was 130562)
Discontinuity: Block 60928 is at 165891 (was 163839)
Discontinuity: Block 90368 is at 197634 (was 195330)
Discontinuity: Block 121856 is at 232448 (was 229121)
Discontinuity: Block 150528 is at 263170 (was 261119)
Discontinuity: Block 181504 is at 296963 (was 294145)
Discontinuity: Block 210944 is at 328706 (was 326402)
Discontinuity: Block 241664 is at 361474 (was 359425)
Discontinuity: Block 272896 is at 395264 (was 392705)
Discontinuity: Block 303360 is at 427010 (was 425727)
Discontinuity: Block 334080 is at 459778 (was 457729)
Discontinuity: Block 365568 is at 493568 (was 491265)
Discontinuity: Block 395264 is at 525314 (was 523263)
Discontinuity: Block 426240 is at 558082 (was 556289)
....
for an 8192x1M (8G) buffered dd, I now get 88 extents, in order.
Do you want the mballoc history?
Now I can try some multithreaded tests :)
Thanks,
-Eric
> thanks, Alex
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists