From: Karel Zak <kzak@redhat.com>
To: Dongsu Park <dongsu.park@profitbricks.com>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
linux-ext4@vger.kernel.org, tytso@mit.edu,
Lukas Czerner <lczerner@redhat.com>,
Namjae Jeon <namjae.jeon@samsung.com>,
Ashish Sangwan <a.sangwan@samsung.com>
Subject: Re: [PATCH] util-linux/fallocate: introduce an option -c to support FALLOC_FL_COLLAPSE_RANGE
Date: Thu, 27 Feb 2014 10:00:05 +0100 [thread overview]
Message-ID: <20140227090005.GH32036@x2.net.home> (raw)
In-Reply-To: <1393355305-12009-1-git-send-email-dongsu.park@profitbricks.com>
On Tue, Feb 25, 2014 at 08:08:25PM +0100, Dongsu Park wrote:
> Introduce a new option -c (or --collapse-range) to support a new flag
> FALLOC_FL_COLLAPSE_RANGE for fallocate(2). It will nullify a particular
> range [offset, offset+len] by shifting extents beyond the range to the
> beginning of the hole.
Thanks!
> To test that, it's necessary to apply kernel patches in the patchset
We (util-linux) always waiting for new stuff in Linus tree :-)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2014-02-27 9:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 5:44 [PATCH RESEND 3/10] ext4: Add support FALLOC_FL_COLLAPSE_RANGE for fallocate Namjae Jeon
2014-02-10 23:34 ` Dave Chinner
2014-02-11 11:59 ` Lukáš Czerner
2014-02-12 2:28 ` Namjae Jeon
2014-02-18 9:05 ` Lukáš Czerner
2014-02-18 9:46 ` Dave Chinner
2014-02-18 9:50 ` Namjae Jeon
2014-02-18 14:30 ` Theodore Ts'o
2014-02-19 1:08 ` Namjae Jeon
2014-02-25 19:08 ` [PATCH] util-linux/fallocate: introduce an option -c to support FALLOC_FL_COLLAPSE_RANGE Dongsu Park
2014-02-25 19:31 ` Dave Chinner
2014-02-27 10:27 ` Dongsu Park
2014-02-27 3:59 ` Namjae Jeon
2014-02-27 10:35 ` [PATCH v2] util-linux/fallocate: introduce an option -c to support COLLAPSE_RANGE Dongsu Park
2014-04-18 10:52 ` Karel Zak
2014-02-27 9:00 ` Karel Zak [this message]
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=20140227090005.GH32036@x2.net.home \
--to=kzak@redhat.com \
--cc=a.sangwan@samsung.com \
--cc=dongsu.park@profitbricks.com \
--cc=lczerner@redhat.com \
--cc=linkinjeon@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=tytso@mit.edu \
--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).