[lkml]   [2001]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: O_TRUNC problem on a full filesystem

On Thu, May 24, 2001 at 11:24:10AM -0600, Andreas Dilger wrote:

> How have you done the ext3 preallocation code?

Preallocation is currently disabled in ext3. Eventually I'll probably
get it going by adding a journal prepare-commit callback to allow the
filesystem to flush preallocation before committing.

> One way to do it would be
> to only mark the blocks as used in the in-memory copy of the block bitmap
> and not write that to disk (we keep 2 copies of the block bitmap, IIRC).

Indeed; I'd need to keep 3 copies to make that work. The state
machine just gets even uglier. :-) I thought about it and I might
still end up going that route.

> Did you ever benchmark ext2 with and without preallocation to see if it
> made any difference? No point in doing extra work if there is no benefit.

The point is not just performance, but also cpu cost (which
preallocation definitely wins on) and on fragmentation if you have
multiple writers in the same directory.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:53    [W:0.109 / U:9.380 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site