From: Tao Ma <tm@tao.ma>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: XFS status update for January 2011
Date: Mon, 14 Feb 2011 10:17:26 +0800 [thread overview]
Message-ID: <4D5890B6.2090105@tao.ma> (raw)
In-Reply-To: <20110213184219.GA22792@infradead.org>
Hi Christoph,
On 02/14/2011 02:42 AM, Christoph Hellwig wrote:
> On the 4th of January we saw the release of Linux 2.6.37, which contains a
> large XFS update:
>
> 67 files changed, 1424 insertions(+), 1524 deletions(-)
>
> User visible changes are the new XFS_IOC_ZERO_RANGE ioctl which allows
> to convert already allocated space into unwritten extents that return
> zeros on a read,
>
would you mind describing some scenario that this ioctl can be used. I am
just wondering whether ocfs2 can implement it as well.
Regards,
Tao
next prev parent reply other threads:[~2011-02-14 2:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 18:42 XFS status update for January 2011 Christoph Hellwig
2011-02-14 2:17 ` Tao Ma [this message]
2011-02-14 12:02 ` Dave Chinner
2011-02-14 15:20 ` tm
2011-02-14 23:55 ` Dave Chinner
2011-02-15 2:01 ` Tao Ma
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=4D5890B6.2090105@tao.ma \
--to=tm@tao.ma \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).