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 v10 0/5] gfs2 iomap write support
Date: Sun, 24 Jun 2018 21:00:23 +0200 [thread overview]
Message-ID: <20180624190028.4166-1-agruenba@redhat.com> (raw)
Here's another update of my gfs2 iomap write patches on top of:
git://git.infradead.org/users/hch/xfs.git gfs2-iomap
Changes since v9:
* Some more gfs2 iomap cleanups.
* Incorporate some feedback from Christoph.
Changes since v8:
* Rebase on top of Christoph's branch.
* New patch to add private pointer to struct 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.
These 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 (5):
gfs2: Further iomap cleanups
gfs2: iomap buffered write support
gfs2: gfs2_extent_length cleanup
gfs2: iomap direct I/O support
gfs2: Remove gfs2_write_{begin,end}
fs/gfs2/aops.c | 331 ++---------------------------------------
fs/gfs2/aops.h | 19 +++
fs/gfs2/bmap.c | 394 ++++++++++++++++++++++++++++++++++++++++---------
fs/gfs2/file.c | 166 +++++++++++++++++++--
4 files changed, 510 insertions(+), 400 deletions(-)
create mode 100644 fs/gfs2/aops.h
--
2.17.1
next reply other threads:[~2018-06-24 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 19:00 Andreas Gruenbacher [this message]
2018-06-24 19:00 ` [PATCH v10 1/5] gfs2: Further iomap cleanups Andreas Gruenbacher
2018-06-25 13:27 ` Andreas Gruenbacher
2018-06-27 1:05 ` Andreas Gruenbacher
2018-06-24 19:00 ` [PATCH v10 2/5] gfs2: iomap buffered write support Andreas Gruenbacher
2018-06-24 19:00 ` [PATCH v10 3/5] gfs2: gfs2_extent_length cleanup Andreas Gruenbacher
2018-06-24 19:00 ` [PATCH v10 4/5] gfs2: iomap direct I/O support Andreas Gruenbacher
2018-06-24 19:00 ` [PATCH v10 5/5] gfs2: Remove gfs2_write_{begin,end} Andreas Gruenbacher
2018-06-29 19:51 ` [Cluster-devel] [PATCH v10 0/5] gfs2 iomap write support Bob Peterson
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=20180624190028.4166-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).