From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel@redhat.com, Christoph Hellwig <hch@lst.de>
Cc: Andreas Gruenbacher <agruenba@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: [PATCH v3 0/8] gfs2 iomap write support
Date: Fri, 23 Mar 2018 20:17:20 +0100 [thread overview]
Message-ID: <20180323191728.23819-1-agruenba@redhat.com> (raw)
Here is an update of my gfs2 iomap write patch queue, with support for
buffered writes as well as direct I/O reads and writes through iomap.
The patches seem to be working well; please review so that we can merge
them in due time.
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
Thanks,
Andreas
Andreas Gruenbacher (8):
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
gfs2: Implement iomap direct I/O support
gfs2: Remove gfs2_write_{begin,end}
iomap: Complete partial direct I/O writes synchronously
fs/ext2/inode.c | 2 +
fs/ext4/inode.c | 2 +
fs/gfs2/aops.c | 336 ++----------------------------------
fs/gfs2/aops.h | 22 +++
fs/gfs2/bmap.c | 470 ++++++++++++++++++++++++++++++++++++++++----------
fs/gfs2/bmap.h | 4 +-
fs/gfs2/file.c | 197 ++++++++++++++++++++-
fs/gfs2/inode.c | 4 -
fs/gfs2/log.h | 7 +-
fs/gfs2/quota.c | 5 +-
fs/gfs2/trans.c | 27 +--
fs/iomap.c | 86 +++++----
fs/xfs/xfs_iomap.c | 2 +
include/linux/iomap.h | 22 +++
14 files changed, 705 insertions(+), 481 deletions(-)
create mode 100644 fs/gfs2/aops.h
--
2.14.3
next reply other threads:[~2018-03-23 19:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 19:17 Andreas Gruenbacher [this message]
2018-03-23 19:17 ` [PATCH v3 1/8] gfs2: gfs2_stuffed_write_end cleanup Andreas Gruenbacher
2018-03-23 19:17 ` [PATCH v3 2/8] gfs2: Remove ordered write mode handling from gfs2_trans_add_data Andreas Gruenbacher
2018-03-23 19:17 ` [PATCH v3 3/8] gfs2: Iomap cleanups and improvements Andreas Gruenbacher
2018-04-06 14:06 ` [Cluster-devel] " Bob Peterson
2018-04-06 15:19 ` Andreas Gruenbacher
2018-03-23 19:17 ` [PATCH v3 4/8] iomap: Add write_{begin,end} iomap operations Andreas Gruenbacher
2018-03-23 19:17 ` [PATCH v3 5/8] gfs2: Implement iomap buffered write support Andreas Gruenbacher
2018-04-06 14:44 ` [Cluster-devel] " Bob Peterson
2018-04-06 15:15 ` Andreas Grünbacher
2018-03-23 19:17 ` [PATCH v3 6/8] gfs2: Implement iomap direct I/O support Andreas Gruenbacher
2018-04-06 15:08 ` [Cluster-devel] " Bob Peterson
2018-03-23 19:17 ` [PATCH v3 7/8] gfs2: Remove gfs2_write_{begin,end} Andreas Gruenbacher
2018-03-23 19:17 ` [PATCH v3 8/8] iomap: Complete partial direct I/O writes synchronously 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=20180323191728.23819-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).