On Wed, 2002-05-01 at 22:14, Eric W. Biederman wrote:
> Stephen Lord <email@example.com> writes:
> > Most of the performance benefits of delayed allocate are that
> > you do not the hard work of allocating the disk space in each
> > write call, you get to do it once, in potentially larger chunks,
> > and often not in the user's context.
> Except for moving the work out of the users context, ext2 gets
> a similar benefit by reserving disk space ahead of time. So it isn't
> clear that you need to have a delayed allocation to achieve this.
Doesn't everyone reserve more than the write asks for?
Delayed allocation as implemented in XFS means that during a write
call which has to make more room in a file, a super block counter
is changed, and the extent information is recorded in an in memory
structure associated with the inode.
Yes, if you have all your metadata buffers sitting in memory and are
not journalling changes then all you are doing is a different set of
memory manipulations which are noise on modern cpus when compared with
actually moving the file data out to disk.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 07 2002 - 22:00:12 EST