On Wed, Jan 17, 2007 at 02:20:43PM -0800, Mingming Cao wrote: > Amit K. Arora wrote: > > If we go with ioctl interface, we need to chose the return > >value from the ioctl. We should either return "0" for success and > >errno for failure, or we should be returning number of bytes > >preallocated. > > Now I am more prefer just return 0 for success. Returning the number of > bytes preallocated back to userspace might be helpful in the case when > the specified window contains blocks already being allocated, but this > should not be a common case. Agreed. Even xfs preallocation ioctl and posix_fallocate return 0 on success. > >(2) Also, we need to decide on what should happen in case of a > >partial success scenario. i.e. after few blocks get preallocated, we hit > >some error - say ENOSPC. Should the call just return the number of bytes > >preallocated, or should it "undo" the partial preallocation and then > >exit with error code ? > > > I think we should try to avoid this partial preallocation at the first > place. Probably checking the number of free blocks before calling > ext4_ext_get_blocks() and returns -ENOSPC if there isn't enough free > blocks to allocate. Otherwise, if it still hits ENOSPC error, I think it > doesn't hurt to leave the partial preallocated blocks there. True. But, there might be a small issue with this. Before calling ext4_ext_get_blocks(), we really don't know how many of the requested blocks are already allocated. Consider a scenario where out of 100 blocks requested for preallocation, say, only 10 need to be physically allocated (90 being already allocated to the file). Now, we will be checking for 100 free blocks in the filesystem, whereas ideally we should be checking for only 10. -- Regards, Amit Arora - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
