[Top] [All Lists]

[PATCH RESEND 0/12] fs: Introduce FALLOC_FL_INSERT_RANGE for fallocate

To: david@xxxxxxxxxxxxx, tytso@xxxxxxx
Subject: [PATCH RESEND 0/12] fs: Introduce FALLOC_FL_INSERT_RANGE for fallocate
From: Namjae Jeon <linkinjeon@xxxxxxxxx>
Date: Tue, 17 Feb 2015 00:47:47 +0900
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, a.sangwan@xxxxxxxxxxx, bfoster@xxxxxxxxxx, mtk.manpages@xxxxxxxxx, linux-man@xxxxxxxxxxxxxxx, linux-api@xxxxxxxxxxxxxxx, Namjae Jeon <linkinjeon@xxxxxxxxx>, Namjae Jeon <namjae.jeon@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id; bh=MqcrjWBqMiszn6LMQz71fC6Io4pC1UoHKru14CZ6Ahw=; b=YbdOa2MJWLih84bWheNkBA/RzNW+LtuS5FgYUygJedxhmjq7gClUaVRNtoIfc/UL2q qtx7xL+zi2+IQfIjrMN7yOcrCzrWqs2a+K555uTFlC6WVPhjqzdZ9Orxcb3jW2UYHvAB H2z3bx7kXhqVzdCHIjqrwXU6RhtW20QoMA8nV2vgnN9Q9vSLbeOHtQkBHS0tpXf4GjGx tY59ntmQPUG1ojuov/pS/zak9ZptT/q7KVCQlUyMWdcrHaxRRzNo1cut9a8H+Ptxud2U OwlLqStcuQiIhjkN1WYUTFPw7ES9M2V6GbTaFF5+hH1M5RiyrOeTczUfut5aHiayIEWK rVzw==
From: Namjae Jeon <namjae.jeon@xxxxxxxxxxx>

In continuation of the work of making the process of non linear editing of
media files faster, we introduce here the new flag FALLOC_FL_INSERT_RANGE
for fallocate.

This flag will work opposite to the FALLOC_FL_COLLAPSE_RANGE flag.
As such, specifying FALLOC_FL_INSERT_RANGE flag will create new space inside 
by inserting a hole within the range specified by offset and len. 
User can write new data in this space. e.g. ads.
Like collapse range, currently we have the limitation that offset and len should
be block size aligned for both XFS and Ext4.

The semantics of the flag are :
1) It creates space within file by inserting a hole of  len bytes starting
   at offset byte without overwriting any existing data. All the data blocks
   from offset to EOF are shifted towards right to make hole space.
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
   in case of xfs and ext4.
4) Insert range does not work for the case when offset is overlapping/beyond
   i_size. If the user wants to insert space at the end of file they are
   advised to use either ftruncate(2) or fallocate(2) with mode 0.
5) It increses the size of file by len bytes.

Namjae Jeon (12):
 fs: Add support FALLOC_FL_INSERT_RANGE for fallocate
 xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate
 ext4: Add support FALLOC_FL_INSERT_RANGE for fallocate
 xfsprog: xfsio: update xfs_io manpage for FALLOC_FL_INSERT_RANGE
 xfstests: generic/042: Standard insert range tests
 xfstests: generic/043: Delayed allocation insert range
 xfstests: generic/044: Multi insert range tests
 xfstests: generic/045: Delayed allocation multi insert
 xfstests: generic/046: Test multiple fallocate insert/collapse range calls
 xfstests: fsstress: Add fallocate insert range operation
 xfstests: fsx: Add fallocate insert range operation
 manpage: update FALLOC_FL_INSERT_RANGE flag in fallocate

<Prev in Thread] Current Thread [Next in Thread>