From: Dave Chinner <david@fromorbit.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: tytso@mit.edu, Namjae Jeon <namjae.jeon@samsung.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com, bpm@sgi.com,
adilger.kernel@dilger.ca, mtk.manpages@gmail.com,
lczerner@redhat.com, linux-fsdevel@vger.kernel.org, jack@suse.cz,
linux-ext4@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v5 0/10] fs: Introduce new flag(FALLOC_FL_COLLAPSE_RANGE) for fallocate
Date: Mon, 24 Feb 2014 11:57:10 +1100 [thread overview]
Message-ID: <20140224005710.GH4317@dastard> (raw)
In-Reply-To: <1392741436-19995-1-git-send-email-linkinjeon@gmail.com>
On Wed, Feb 19, 2014 at 01:37:16AM +0900, Namjae Jeon wrote:
> From: Namjae Jeon <namjae.jeon@samsung.com>
>
> This patch series is in response of the following post:
> http://lwn.net/Articles/556136/
> "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
> in case of xfs and ext4.
> 4) Collaspe range does not work beyond i_size.
>
> 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 (10):
> fs: Add new flag(FALLOC_FL_COLLAPSE_RANGE) for fallocate
> xfs: Add support FALLOC_FL_COLLAPSE_RANGE for fallocate
I've pushed these to the following branch:
git://oss.sgi.com/xfs/xfs.git xfs-collapse-range
And so they'll be in tomorrow's linux-next tree.
> ext4: Add support FALLOC_FL_COLLAPSE_RANGE for fallocate
I've left this one alone for the ext4 guys to sort out.
> xfsprog: xfsio: Add support FALLOC_FL_COLLAPSE_RANGE for fallocate
That's already in a current xfstests tree.
> xfstest: shared/001: Standard collapse range tests
> xfstest: shared/002: Delayed allocation collapse range
> xfstest: shared/003: Multi collapse range tests
> xfstest: shared/004: Delayed allocation multi collapse
> xfstest: shared/005: Test multiple fallocate collapse
These are now in the xfstests git tree.
> manpage: update FALLOC_FL_COLLAPSE_RANGE flag in fallocate
And Michael will need to review and commit that to the kernel
manpages tree.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-02-24 0:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 16:37 [PATCH v5 0/10] fs: Introduce new flag(FALLOC_FL_COLLAPSE_RANGE) for fallocate Namjae Jeon
2014-02-24 0:57 ` Dave Chinner [this message]
2014-02-24 1:34 ` Namjae Jeon
2014-02-25 3:16 ` Stephen Rothwell
2014-02-25 4:13 ` Dave Chinner
2014-02-25 23:23 ` Hugh Dickins
2014-02-25 23:41 ` Andrew Morton
2014-02-26 1:34 ` Dave Chinner
2014-02-26 1:52 ` Andrew Morton
2014-02-26 3:42 ` Dave Chinner
2014-02-26 1:13 ` Dave Chinner
2014-02-26 4:45 ` Hugh Dickins
2014-02-26 6:42 ` Dave Chinner
2014-02-26 23:08 ` Hugh Dickins
2014-02-27 1:24 ` Dave Chinner
2014-02-27 1:30 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140224005710.GH4317@dastard \
--to=david@fromorbit.com \
--cc=adilger.kernel@dilger.ca \
--cc=bpm@sgi.com \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linkinjeon@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=namjae.jeon@samsung.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).