From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel@redhat.com
Cc: Christoph Hellwig <hch@lst.de>,
Dave Chinner <dchinner@redhat.com>,
linux-fsdevel@vger.kernel.org,
Andreas Gruenbacher <agruenba@redhat.com>
Subject: [PATCH v2 0/6] gfs2 iomap buffered write support
Date: Mon, 29 Jan 2018 23:18:38 +0100 [thread overview]
Message-ID: <20180129221844.19476-1-agruenba@redhat.com> (raw)
Hello,
this patch queue converts gfs2 to use iomap for buffered writes, which
uses multi-page block allocations for large writes instead of a separate
allocation for each page of data.
Apply on top of the current gfs2 for-next branch:
https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/log/?h=for-next
Changes since v1:
* Add write_begin and write_end iomap operations instead of the minimal
iomap_written operation from the prevous patch queue. These
operations need to be wired up by filesystems that implement writes
over iomap.
* Several bug fixes in the gfs2 specific patches.
This patch queue doesn't convert direct I/O, so we still have a
remaining user of the old gfs2_write_begin / gfs2_write_end interface
left. Once direct I/O is converted to iomap, we'll get rid of some more
old code.
Thanks,
Andreas
Andreas Gruenbacher (6):
gfs2: gfs2_stuffed_write_end cleanup
gfs2: Remove ordered write mode handling from gfs2_trans_add_data
gfs2: Iomap cleanups and improvements
iomap: Add write_{begin,end} iomap operations
gfs2: Implement iomap buffered write support (1)
gfs2: Implement iomap buffered write support (2)
fs/ext2/inode.c | 2 +
fs/ext4/inode.c | 2 +
fs/gfs2/aops.c | 154 +++++++++++++++-----
fs/gfs2/aops.h | 19 +++
fs/gfs2/bmap.c | 392 ++++++++++++++++++++++++++++++++++++++------------
fs/gfs2/bmap.h | 5 +-
fs/gfs2/file.c | 47 +++++-
fs/gfs2/inode.c | 4 -
fs/gfs2/log.h | 7 +-
fs/gfs2/quota.c | 5 +-
fs/gfs2/trans.c | 27 ++--
fs/iomap.c | 62 +++++---
fs/xfs/xfs_iomap.c | 2 +
include/linux/iomap.h | 22 +++
14 files changed, 571 insertions(+), 179 deletions(-)
create mode 100644 fs/gfs2/aops.h
--
2.14.3
next reply other threads:[~2018-01-29 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 22:18 Andreas Gruenbacher [this message]
2018-01-29 22:18 ` [PATCH v2 1/6] gfs2: gfs2_stuffed_write_end cleanup Andreas Gruenbacher
2018-01-29 22:18 ` [PATCH v2 2/6] gfs2: Remove ordered write mode handling from gfs2_trans_add_data Andreas Gruenbacher
2018-01-29 22:18 ` [PATCH v2 3/6] gfs2: Iomap cleanups and improvements Andreas Gruenbacher
2018-01-29 22:18 ` [PATCH v2 4/6] iomap: Add write_{begin,end} iomap operations Andreas Gruenbacher
2018-01-29 22:18 ` [PATCH v2 5/6] gfs2: Implement iomap buffered write support (1) Andreas Gruenbacher
2018-01-29 22:18 ` [PATCH v2 6/6] gfs2: Implement iomap buffered write support (2) 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=20180129221844.19476-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=dchinner@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).