xfs
[Top] [All Lists]

Re: XFS status update for January 2011

To: "Dave Chinner" <david@xxxxxxxxxxxxx>
Subject: Re: XFS status update for January 2011
From: tm@xxxxxx
Date: Mon, 14 Feb 2011 08:20:18 -0700
Cc: "Tao Ma" <tm@xxxxxx>, "Christoph Hellwig" <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=tao.ma; h=Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance:X-Identified-User; b=My+P3ZiLxy/ZDJzKE20+OjTJKOJ/krzp9m/PXCaZl8/9zHL0BEz17Rs+U5kFntSSi+M00ygBzId39xqoZ3L14TKlZf3eG19astsMYITO4cTh9UUXtkZs+Q0rBHPCw60n;
Importance: Normal
In-reply-to: <20110214120237.GB13052@dastard>
References: <20110213184219.GA22792@xxxxxxxxxxxxx> <4D5890B6.2090105@xxxxxx> <20110214120237.GB13052@dastard>
User-agent: SquirrelMail/1.4.21
Hi Dave,
> On Mon, Feb 14, 2011 at 10:17:26AM +0800, Tao Ma wrote:
>> 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.
>
> Zeroing a file without doing IO or having to punch out the blocks
> already allocated to the file.
>
> In this case, we had a couple of different people in cloud storage
> land asking for such functionality to optimise record deletion
> be avoiding disruption of their preallocated file layouts as a
> punch-then-preallocate operation does.
Thanks for the info. yeah, ocfs2 is also used to host images in some cloud
computing environment. So It looks helpful for us too.
>
> If you you have some kind of use for it in ocfs2, then implementing
> the XFS ioctl is not the correct thing to do - using the fallocate
> patch I've had sitting around (since about 15min after creating the
> XFS ioctl) is most likely the right way to proceed....
yeah, Josef has added the punching hole in fallocate, so I guess another
parameter for keeping the blocks during hole punching should be enough for
us. :)

Regards,
Tao

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