linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v6 0/9] gfs2 iomap write support
Date: Sat,  2 Jun 2018 11:57:08 +0200	[thread overview]
Message-ID: <20180602095717.31641-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 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-rc7 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 (8):
  iomap: Mark newly allocated buffer heads as new
  iomap: Complete partial direct I/O writes synchronously
  iomap: Generic inline data handling
  iomap: Add write_end iomap operation
  gfs2: iomap buffered write support
  gfs2: gfs2_extent_length cleanup
  gfs2: iomap direct I/O support
  gfs2: Remove gfs2_write_{begin,end}

Christoph Hellwig (1):
  iomap: inline data should be an iomap type, not a flag

 fs/buffer.c                 |  28 +--
 fs/ext2/inode.c             |   1 +
 fs/ext4/inline.c            |   4 +-
 fs/ext4/inode.c             |   1 +
 fs/gfs2/aops.c              | 328 ++------------------------------
 fs/gfs2/aops.h              |  22 +++
 fs/gfs2/bmap.c              | 367 +++++++++++++++++++++++++++++++-----
 fs/gfs2/file.c              | 168 ++++++++++++++++-
 fs/iomap.c                  | 133 ++++++++++---
 fs/xfs/xfs_iomap.c          |   1 +
 include/linux/buffer_head.h |   3 +
 include/linux/iomap.h       |  15 +-
 12 files changed, 654 insertions(+), 417 deletions(-)
 create mode 100644 fs/gfs2/aops.h

-- 
2.17.0

             reply	other threads:[~2018-06-02  9:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-02  9:57 Andreas Gruenbacher [this message]
2018-06-02  9:57 ` [PATCH v6 1/9] iomap: inline data should be an iomap type, not a flag Andreas Gruenbacher
2018-06-02  9:57 ` [PATCH v6 2/9] iomap: Mark newly allocated buffer heads as new Andreas Gruenbacher
2018-06-02 16:58   ` Christoph Hellwig
2018-06-02  9:57 ` [PATCH v6 3/9] iomap: Complete partial direct I/O writes synchronously Andreas Gruenbacher
2018-06-02 16:58   ` Christoph Hellwig
2018-06-02  9:57 ` [PATCH v6 4/9] iomap: Generic inline data handling Andreas Gruenbacher
2018-06-02 17:04   ` Christoph Hellwig
2018-06-04 12:02     ` Andreas Grünbacher
2018-06-04 12:12       ` Christoph Hellwig
2018-06-04 17:01         ` Andreas Grünbacher
2018-06-02  9:57 ` [PATCH v6 5/9] iomap: Add write_end iomap operation Andreas Gruenbacher
2018-06-02 17:06   ` Christoph Hellwig
2018-06-04 12:03     ` Andreas Grünbacher
2018-06-02  9:57 ` [PATCH v6 6/9] gfs2: iomap buffered write support Andreas Gruenbacher
2018-06-02  9:57 ` [PATCH v6 7/9] gfs2: gfs2_extent_length cleanup Andreas Gruenbacher
2018-06-02  9:57 ` [PATCH v6 8/9] gfs2: iomap direct I/O support Andreas Gruenbacher
2018-06-02  9:57 ` [PATCH v6 9/9] gfs2: Remove gfs2_write_{begin,end} Andreas Gruenbacher

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=20180602095717.31641-1-agruenba@redhat.com \
    --to=agruenba@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).