[PATCH 0/3] fs: New flag FALLOC_FL_COLLAPSE_RANGE for fallocate
From: Namjae Jeon
Date: Wed Jul 31 2013 - 10:42:03 EST
From: Namjae Jeon <namjae.jeon@xxxxxxxxxxx>
This patch series is in response of the following post:
"ext4: introduce two new ioctls"
Dave chinner suggested that truncate_block_range (which was one of the ioctls name)
should be an fallocate operation and not any fs specific ioctl, hence
we add this functionality to fallocate.
This patch series introduces new flag FALLOC_FL_COLLAPSE_RANGE for fallocate
and implements it for XFS and Ext4.
The semantics of this flag are following:
1) It collapses the range lying between offset and length by removing any data
blocks which are present in this range and than updates all the logical
offsets of extents beyond "offset + len" to nullify the hole created by
removing blocks. In short, it does not leave a hole.
2) It should be used exclusively. No other fallocate flag in combination.
3) Offset and length supplied to fallocate should be fs block size aligned.
4) It wokrs beyond "EOF", so the extents which are pre-allocated beyond "EOF"
are also updated.
5) It reduces the i_size of inode by the amount of collapse range which lies
within i_size. So, if offset >= i_size, i_size won't be changed at all.
This new functionality of collapsing range could be used by media editing tools
which does non linear editing to quickly purge and edit parts of a media file.
This will immensely improve the performance of these operations.
The limitation of fs block size aligned offsets can be easily handled
by media codecs which are encapsulated in a conatiner as they have to
just change the offset to next keyframe value to match the proper alignment.
Namjae Jeon (3):
fs: Introduce new flag FALLOC_FL_COLLAPSE_RANGE
xfs: Implement FALLOC_FL_COLLAPSE_RANGE
ext4: Implement FALLOC_FL_COLLAPSE_RANGE
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/