xfs
[Top] [All Lists]

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

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [PATCH 0/3] fs: Introduce FALLOC_FL_INSERT_RANGE for fallocate
From: Namjae Jeon <linkinjeon@xxxxxxxxx>
Date: Tue, 1 Apr 2014 09:19:12 +0900
Cc: Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>, "Theodore Ts'o" <tytso@xxxxxxx>, "adilger.kernel@xxxxxxxxx" <adilger.kernel@xxxxxxxxx>, Jan Kara <jack@xxxxxxx>, LukÃÅ Czerner <lczerner@xxxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, "linux-ext4@xxxxxxxxxxxxxxx" <linux-ext4@xxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, 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=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MIxg4klPAuS2BIvVbl6Lv1jzw6pg3b4nz0kYLA9tlcU=; b=c/4aYmNmTAMt0zhSKgxrpOGNM1dZ6uPiAMtonfZzAUH3KczlufBT/ejaFCgY0xwS4l gnt6SxKlCxHtRcSc4R6OWEKJvao1eP7DQkUXWWWn3eJdpRL8+01qYEHvJpc3maCdCh8D 9Ntbmz73p2Lh5ZiqJ3SUgW1IswobtOZzzPDZvgOHKRINitEonAv5EkSTEnfDhvJx0b8T kQ4y7+YaULxph9teN3Yv2G46yhiIaDcTHEKqQ0RXfZQGw8LU4f78gTHq0h19QBLycP4I QWK7gk/a0ve8RNbeu4g5E+KAutrV2JULzi075y4nlXD28ORdbljk8zZdVIYKDJF0xPut 4R/Q==
In-reply-to: <20140331145625.GA10791@xxxxxxxxxxxxx>
References: <1396277611-10759-1-git-send-email-linkinjeon@xxxxxxxxx> <20140331145625.GA10791@xxxxxxxxxxxxx>
2014-03-31 23:56 GMT+09:00 Christoph Hellwig <hch@xxxxxxxxxxxxx>:
> 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?
>
Hi Christoph.
Sure, I'm planning to introduce FS_IOC_MOVE_DATA ioctl that can split
file as well as merging for xfs and ext4.
I already started to implement it. and will post it soon.

Thanks.

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