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 v8 00/10] gfs2 iomap write support
Date: Mon, 4 Jun 2018 21:31:13 +0200 [thread overview]
Message-ID: <20180604193123.27655-1-agruenba@redhat.com> (raw)
Here's another update of my gfs2 iomap write patches, with support for
buffered writes as well as direct I/O reads and writes through iomap.
Changes since v7:
* Drop patch that allows to unconditionally mark the inode dirty in
__generic_write_end and mark the inode dirty in
iomap_write_inline_data instead.
* Call the page_write_end hook even for IOMAP_INLINE mappings.
* Drop patch "iomap: Put struct iomap_ops into struct 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 (8):
iomap: Mark newly allocated buffer heads as new
iomap: Complete partial direct I/O writes synchronously
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}
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 | 76 ++++-----
fs/ext4/inline.c | 4 +-
fs/gfs2/aops.c | 328 ++-----------------------------------
fs/gfs2/aops.h | 22 +++
fs/gfs2/bmap.c | 365 ++++++++++++++++++++++++++++++++++++------
fs/gfs2/file.c | 168 +++++++++++++++++--
fs/internal.h | 2 +
fs/iomap.c | 136 ++++++++++++----
include/linux/iomap.h | 11 +-
9 files changed, 672 insertions(+), 440 deletions(-)
create mode 100644 fs/gfs2/aops.h
--
2.17.0
next reply other threads:[~2018-06-04 19:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 19:31 Andreas Gruenbacher [this message]
2018-06-04 19:31 ` [PATCH v8 01/10] iomap: inline data should be an iomap type, not a flag Andreas Gruenbacher
2018-06-04 19:31 ` [PATCH v8 02/10] iomap: Mark newly allocated buffer heads as new Andreas Gruenbacher
2018-06-04 19:31 ` [PATCH v8 03/10] iomap: Complete partial direct I/O writes synchronously Andreas Gruenbacher
2018-06-05 12:10 ` David Sterba
2018-06-05 12:32 ` Andreas Grünbacher
2018-06-06 10:26 ` Christoph Hellwig
2018-06-06 11:44 ` Andreas Gruenbacher
2018-06-04 19:31 ` [PATCH v8 04/10] fs: factor out a __generic_write_end helper Andreas Gruenbacher
2018-06-04 19:31 ` [PATCH v8 05/10] iomap: Generic inline data handling Andreas Gruenbacher
2018-06-05 5:34 ` Christoph Hellwig
2018-06-04 19:31 ` [PATCH v8 06/10] iomap: Add page_write_end iomap hook Andreas Gruenbacher
2018-06-05 7:56 ` Andreas Grünbacher
2018-06-05 12:07 ` David Sterba
2018-06-05 12:17 ` Andreas Grünbacher
2018-06-05 12:29 ` David Sterba
2018-06-05 12:50 ` Andreas Grünbacher
2018-06-04 19:31 ` [PATCH v8 07/10] gfs2: iomap buffered write support Andreas Gruenbacher
2018-06-04 19:31 ` [PATCH v8 08/10] gfs2: gfs2_extent_length cleanup Andreas Gruenbacher
2018-06-04 19:31 ` [PATCH v8 09/10] gfs2: iomap direct I/O support Andreas Gruenbacher
2018-06-04 19:31 ` [PATCH v8 10/10] 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=20180604193123.27655-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).