All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v7 00/12] gfs2 iomap write support
Date: Mon,  4 Jun 2018 14:37:17 +0200	[thread overview]
Message-ID: <20180604123729.23414-1-agruenba@redhat.com> (raw)

Here's an update of my gfs2 iomap write patches, with support for
buffered writes as well as direct I/O reads and writes through iomap.


Significant changes since v6:

 * Switch to Christoph's patch for splitting out __generic_write_end and 
   put the inode-dirtying change in a separate commit.

 * Switch froma mandatory write_end operation to an optional
   page_write_end hook.

 * Add a patch to pass struct iomap_ops in struct iomap at the end for
   demonstration purposes.


Significant changes since v5:

 * Initial gfs2 specific cleanups split off and posted separately.

 * New patch for generic iomap inline data handling.

 * Iomap write_begin operation removed.


A 4.17 based version of the patches can be found here:

  https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/log/?h=iomap-write

Thanks,
Andreas

Andreas Gruenbacher (10):
  iomap: Mark newly allocated buffer heads as new
  iomap: Complete partial direct I/O writes synchronously
  fs: allow to always dirty inode in __generic_write_end
  iomap: Generic inline data handling
  iomap: Add page_write_end iomap hook
  gfs2: iomap buffered write support
  gfs2: gfs2_extent_length cleanup
  gfs2: iomap direct I/O support
  gfs2: Remove gfs2_write_{begin,end}
  iomap: Pass struct iomap_ops to iomap actors

Christoph Hellwig (2):
  iomap: inline data should be an iomap type, not a flag
  fs: factor out a __generic_write_end helper

 fs/buffer.c           |  75 ++++-----
 fs/dax.c              |   8 +-
 fs/ext4/inline.c      |   4 +-
 fs/gfs2/aops.c        | 328 ++-----------------------------------
 fs/gfs2/aops.h        |  22 +++
 fs/gfs2/bmap.c        | 368 ++++++++++++++++++++++++++++++++++++------
 fs/gfs2/file.c        | 172 ++++++++++++++++++--
 fs/internal.h         |   2 +
 fs/iomap.c            |  99 +++++++++---
 include/linux/iomap.h |  13 +-
 10 files changed, 653 insertions(+), 438 deletions(-)
 create mode 100644 fs/gfs2/aops.h

-- 
2.17.0



WARNING: multiple messages have this Message-ID (diff)
From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel@redhat.com, Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel@vger.kernel.org, Andreas Gruenbacher <agruenba@redhat.com>
Subject: [PATCH v7 00/12] gfs2 iomap write support
Date: Mon,  4 Jun 2018 14:37:17 +0200	[thread overview]
Message-ID: <20180604123729.23414-1-agruenba@redhat.com> (raw)

Here's an update of my gfs2 iomap write patches, with support for
buffered writes as well as direct I/O reads and writes through iomap.


Significant changes since v6:

 * Switch to Christoph's patch for splitting out __generic_write_end and 
   put the inode-dirtying change in a separate commit.

 * Switch froma mandatory write_end operation to an optional
   page_write_end hook.

 * Add a patch to pass struct iomap_ops in struct iomap at the end for
   demonstration purposes.


Significant changes since v5:

 * Initial gfs2 specific cleanups split off and posted separately.

 * New patch for generic iomap inline data handling.

 * Iomap write_begin operation removed.


A 4.17 based version of the patches can be found here:

  https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/log/?h=iomap-write

Thanks,
Andreas

Andreas Gruenbacher (10):
  iomap: Mark newly allocated buffer heads as new
  iomap: Complete partial direct I/O writes synchronously
  fs: allow to always dirty inode in __generic_write_end
  iomap: Generic inline data handling
  iomap: Add page_write_end iomap hook
  gfs2: iomap buffered write support
  gfs2: gfs2_extent_length cleanup
  gfs2: iomap direct I/O support
  gfs2: Remove gfs2_write_{begin,end}
  iomap: Pass struct iomap_ops to iomap actors

Christoph Hellwig (2):
  iomap: inline data should be an iomap type, not a flag
  fs: factor out a __generic_write_end helper

 fs/buffer.c           |  75 ++++-----
 fs/dax.c              |   8 +-
 fs/ext4/inline.c      |   4 +-
 fs/gfs2/aops.c        | 328 ++-----------------------------------
 fs/gfs2/aops.h        |  22 +++
 fs/gfs2/bmap.c        | 368 ++++++++++++++++++++++++++++++++++++------
 fs/gfs2/file.c        | 172 ++++++++++++++++++--
 fs/internal.h         |   2 +
 fs/iomap.c            |  99 +++++++++---
 include/linux/iomap.h |  13 +-
 10 files changed, 653 insertions(+), 438 deletions(-)
 create mode 100644 fs/gfs2/aops.h

-- 
2.17.0

             reply	other threads:[~2018-06-04 12:37 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 12:37 Andreas Gruenbacher [this message]
2018-06-04 12:37 ` [PATCH v7 00/12] gfs2 iomap write support Andreas Gruenbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 01/12] iomap: inline data should be an iomap type, not a flag Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 02/12] iomap: Mark newly allocated buffer heads as new Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 03/12] iomap: Complete partial direct I/O writes synchronously Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 04/12] fs: factor out a __generic_write_end helper Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 05/12] fs: allow to always dirty inode in __generic_write_end Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:48   ` [Cluster-devel] " Christoph Hellwig
2018-06-04 12:48     ` Christoph Hellwig
2018-06-04 16:24     ` [Cluster-devel] " Andreas Grünbacher
2018-06-04 16:24       ` Andreas Grünbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 06/12] iomap: Generic inline data handling Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 07/12] iomap: Add page_write_end iomap hook Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:50   ` [Cluster-devel] " Christoph Hellwig
2018-06-04 12:50     ` Christoph Hellwig
2018-06-04 16:40     ` [Cluster-devel] " Andreas Grünbacher
2018-06-04 16:40       ` Andreas Grünbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 08/12] gfs2: iomap buffered write support Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 09/12] gfs2: gfs2_extent_length cleanup Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 10/12] gfs2: iomap direct I/O support Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 11/12] gfs2: Remove gfs2_write_{begin, end} Andreas Gruenbacher
2018-06-04 12:37   ` [PATCH v7 11/12] gfs2: Remove gfs2_write_{begin,end} Andreas Gruenbacher
2018-06-04 12:37 ` [Cluster-devel] [PATCH v7 12/12] iomap: Put struct iomap_ops into struct iomap Andreas Gruenbacher
2018-06-04 12:37   ` Andreas Gruenbacher
2018-06-04 12:52   ` [Cluster-devel] " Christoph Hellwig
2018-06-04 12:52     ` Christoph Hellwig
2018-06-04 17:00     ` [Cluster-devel] " Andreas Grünbacher
2018-06-04 17:00       ` Andreas Grünbacher

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=20180604123729.23414-1-agruenba@redhat.com \
    --to=agruenba@redhat.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.