Takes this structure up to 32 bytes on x86. That's a moderate amount of
inode bloat for something which is only used when an application currently
has the inode open for writing.
Have you given any thought to dynamic allocation of the above?
And if we were to do that, there are a few things which we could move out
of the ext3 in-core inode and into the above structure, such as
i_next_alloc_block and i_next_alloc_goal.
Does the reservation code work for directory growth, btw?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/