public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: RFC: use iomap infrastructure for all our zeroing needs
Date: Thu, 14 Apr 2016 07:55:56 +1000	[thread overview]
Message-ID: <20160413215556.GT567@dastard> (raw)
In-Reply-To: <1460500013-28334-1-git-send-email-hch@lst.de>

On Tue, Apr 12, 2016 at 03:26:47PM -0700, Christoph Hellwig wrote:
> This series uses the new iomap infrastructure to simplify all kinds
> of zeroing operations.  The RFC tag is mostly because the DAX path
> modified in this series hasn't been tested yet, the normal buffered
> path has been tested and works fine.

Yep, passes all my testing for normal FS paths, though I haven't run
DAX on it yet, either. I'll look to include this at teh same time as
the map iomap write/fiemap series.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2016-04-13 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 22:26 RFC: use iomap infrastructure for all our zeroing needs Christoph Hellwig
2016-04-12 22:26 ` [PATCH 1/6] iomap: support DAX based zeroing Christoph Hellwig
2016-04-12 22:26 ` [PATCH 2/6] xfs: use iomap infrastructure for DAX zeroing Christoph Hellwig
2016-04-12 22:26 ` [PATCH 3/6] xfs: handle 64-bit length in xfs_iozero Christoph Hellwig
2016-04-12 22:26 ` [PATCH 4/6] xfs: use xfs_zero_range in xfs_zero_eof Christoph Hellwig
2016-04-12 22:26 ` [PATCH 5/6] xfs: split xfs_free_file_space in manageable pieces Christoph Hellwig
2016-04-12 22:26 ` [PATCH 6/6] kill xfs_zero_remaining_bytes Christoph Hellwig
2016-04-13 21:55 ` Dave Chinner [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=20160413215556.GT567@dastard \
    --to=david@fromorbit.com \
    --cc=hch@lst.de \
    --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