From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "hch@lst.de" <hch@lst.de>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Cc: "rpeterso@redhat.com" <rpeterso@redhat.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: iomap infrastructure and multipage writes V4
Date: Wed, 11 May 2016 22:42:37 +0000 [thread overview]
Message-ID: <1463006545.29294.32.camel@intel.com> (raw)
In-Reply-To: <1462783638-4968-1-git-send-email-hch@lst.de>
On Mon, 2016-05-09 at 10:47 +0200, Christoph Hellwig wrote:
> This series add a new file system I/O path that uses the iomap
> structure
> introduced for the pNFS support and support multi-page buffered
> writes.
>
> This was first started by Dave Chinner a long time ago, then I did
> beat
> it into shape for production runs in a very constrained ARM NAS
> enviroment for Tuxera almost as long ago, and now half a dozen
> rewrites
> later it's back.
>
> The basic idea is to avoid the per-block get_blocks overhead
> and make use of extents in the buffered write path by iterating over
> them instead.
>
> Note that patch 1 conflicts with Vishals dax error handling series.
> It would be great to have a stable branch with it so that both the
> XFS and nvdimm tree could pull it in before the other changes in this
> area.
I'm looking to post a stable branch with my patches soon. My patches
depend on Jan's fixes for ext4 and DAX, and as soon as they land in a
stable ext4 branch, I'll create one for dax error handling. In the
meanwhile, v7 of my patches includes your patch 1 updated for the error
handling series.
>
> Changes since V3:
> - fix DAX based zeroing
> - Reviews and trivial fixes from Bob
>
> Changes since V2:
> - fix the range for delalloc punches after failed writes
> - updated some changelogs
>
> Chances since V1:
> - add support for fiemap
> - fix a test fail on 1k block sizes
> - prepare for 64-bit length, this will be used in a follow on
> patchset
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "hch@lst.de" <hch@lst.de>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Cc: "rpeterso@redhat.com" <rpeterso@redhat.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: iomap infrastructure and multipage writes V4
Date: Wed, 11 May 2016 22:42:37 +0000 [thread overview]
Message-ID: <1463006545.29294.32.camel@intel.com> (raw)
In-Reply-To: <1462783638-4968-1-git-send-email-hch@lst.de>
On Mon, 2016-05-09 at 10:47 +0200, Christoph Hellwig wrote:
> This series add a new file system I/O path that uses the iomap
> structure
> introduced for the pNFS support and support multi-page buffered
> writes.
>
> This was first started by Dave Chinner a long time ago, then I did
> beat
> it into shape for production runs in a very constrained ARM NAS
> enviroment for Tuxera almost as long ago, and now half a dozen
> rewrites
> later it's back.
>
> The basic idea is to avoid the per-block get_blocks overhead
> and make use of extents in the buffered write path by iterating over
> them instead.
>
> Note that patch 1 conflicts with Vishals dax error handling series.
> It would be great to have a stable branch with it so that both the
> XFS and nvdimm tree could pull it in before the other changes in this
> area.
I'm looking to post a stable branch with my patches soon. My patches
depend on Jan's fixes for ext4 and DAX, and as soon as they land in a
stable ext4 branch, I'll create one for dax error handling. In the
meanwhile, v7 of my patches includes your patch 1 updated for the error
handling series.
>
> Changes since V3:
> - fix DAX based zeroing
> - Reviews and trivial fixes from Bob
>
> Changes since V2:
> - fix the range for delalloc punches after failed writes
> - updated some changelogs
>
> Chances since V1:
> - add support for fiemap
> - fix a test fail on 1k block sizes
> - prepare for 64-bit length, this will be used in a follow on
> patchset
>
next prev parent reply other threads:[~2016-05-11 22:42 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 8:47 iomap infrastructure and multipage writes V4 Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 01/15] dax: export a low-level __dax_zero_page_range helper Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-11 22:43 ` Verma, Vishal L
2016-05-11 22:43 ` Verma, Vishal L
2016-05-09 8:47 ` [PATCH 02/15] fs: move struct iomap from exportfs.h to a separate header Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 03/15] fs: introduce iomap infrastructure Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 04/15] fs: support DAX based iomap zeroing Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 05/15] xfs: make xfs_bmbt_to_iomap available outside of xfs_pnfs.c Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 06/15] xfs: reorder zeroing and flushing sequence in truncate Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 07/15] xfs: implement iomap based buffered write path Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 08/15] xfs: remove buffered write support from __xfs_get_blocks Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 09/15] fs: iomap based fiemap implementation Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-23 20:09 ` Bob Peterson
2016-05-23 20:09 ` Bob Peterson
2016-05-24 13:10 ` Christoph Hellwig
2016-05-24 13:10 ` Christoph Hellwig
2016-05-26 18:19 ` Bob Peterson
2016-05-26 18:19 ` Bob Peterson
2016-05-26 22:57 ` Dave Chinner
2016-05-26 22:57 ` Dave Chinner
2016-05-09 8:47 ` [PATCH 10/15] xfs: use iomap " Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 11/15] xfs: use iomap infrastructure for DAX zeroing Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 12/15] xfs: handle 64-bit length in xfs_iozero Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 13/15] xfs: use xfs_zero_range in xfs_zero_eof Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 14/15] xfs: split xfs_free_file_space in manageable pieces Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-09 8:47 ` [PATCH 15/15] xfs: kill xfs_zero_remaining_bytes Christoph Hellwig
2016-05-09 8:47 ` Christoph Hellwig
2016-05-11 22:42 ` Verma, Vishal L [this message]
2016-05-11 22:42 ` iomap infrastructure and multipage writes V4 Verma, Vishal L
2016-06-01 6:35 ` Dave Chinner
2016-06-01 6:35 ` Dave Chinner
2016-06-01 12:31 ` Christoph Hellwig
2016-06-01 12:31 ` 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=1463006545.29294.32.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rpeterso@redhat.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.