[Top] [All Lists]

Re: [PATCH 0/3] fs: Introduce FALLOC_FL_INSERT_RANGE for fallocate

To: Namjae Jeon <linkinjeon@xxxxxxxxx>
Subject: Re: [PATCH 0/3] fs: Introduce FALLOC_FL_INSERT_RANGE for fallocate
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 31 Mar 2014 07:56:25 -0700
Cc: viro@xxxxxxxxxxxxxxxxxx, david@xxxxxxxxxxxxx, hch@xxxxxxxxxxxxx, tytso@xxxxxxx, adilger.kernel@xxxxxxxxx, jack@xxxxxxx, lczerner@xxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Namjae Jeon <namjae.jeon@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1396277611-10759-1-git-send-email-linkinjeon@xxxxxxxxx>
References: <1396277611-10759-1-git-send-email-linkinjeon@xxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Mon, Mar 31, 2014 at 11:53:31PM +0900, Namjae Jeon wrote:
> This flag will work opposite to the newly added FALLOC_FL_COLLAPSE_RANGE flag.
> As such, specifying FALLOC_FL_INSERT_RANGE flag will insert zeroed-out space
> in between the file 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.

Btw, I remember Samsung also had an ioctl for XFS to split a file into
two without moving the data, do you plan to submit that one as well?

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