From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/2] xfs: Introduce XFS_IOC_ZERO_RANGE
Date: Tue, 27 Jul 2010 03:59:30 -0400 [thread overview]
Message-ID: <20100727075930.GC30562@infradead.org> (raw)
In-Reply-To: <1280210129-10925-3-git-send-email-david@fromorbit.com>
On Tue, Jul 27, 2010 at 03:55:29PM +1000, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> XFS_IOC_ZERO_RANGE is the equivalent of an atomic XFS_IOC_UNRESVSP/
> XFS_IOC_RESVSP call pair. It enabled ranges of written data to be
> turned into zeroes without requiring IO or having to free and
> reallocate the extents in the range given as would occur if we had
> to punch and then preallocate them separately. This enables
> applications to zero parts of files very quickly without changing
> the layout of the files in any way.
This looks good minus the left over printks. It'll also needs xfstests
coverage and a description in the xfsctl manpage.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-27 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 5:55 [RFC, PATCH 0/2] xfs: Fast zeroing of allocated space Dave Chinner
2010-07-27 5:55 ` [PATCH 1/2] xfs: use range primitives for xfs page cache operations Dave Chinner
2010-07-27 6:53 ` Christoph Hellwig
2010-07-27 12:05 ` Dave Chinner
2010-07-27 5:55 ` [PATCH 2/2] xfs: Introduce XFS_IOC_ZERO_RANGE Dave Chinner
2010-07-27 7:59 ` Christoph Hellwig [this message]
2010-07-27 20:49 ` [RFC, PATCH 0/2] xfs: Fast zeroing of allocated space Alex Elder
-- strict thread matches above, loose matches on Subject: below --
2010-08-03 6:22 [PATCH " Dave Chinner
2010-08-03 6:22 ` [PATCH 2/2] xfs: Introduce XFS_IOC_ZERO_RANGE Dave Chinner
2010-08-03 18:56 ` Christoph Hellwig
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=20100727075930.GC30562@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.