From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/3] gfs2: More iomap enablement
Date: Sat, 7 Jul 2018 11:39:01 +0200 [thread overview]
Message-ID: <20180707093904.23177-1-agruenba@redhat.com> (raw)
Hi,
here's another forward-looking fix and two enablement patches. The
patches depend on the following branches:
xfs-linux/iomap-4.19-merge
linux-gfs/for-next
The "iomap: add initial support for writes without buffer heads" patch
on 'iomap-4.19-merge' introduces the IOMAP_F_BUFFER_HEAD flag which
needds to be set for gfs2. I've done that in the merge commit for that
branch so that we don't end up with any broken commits.
An 'iomap-misc' branch with all those changes can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/log/?h=iomap-misc
The 'iomap-4.19-merge' branch can be found in the xfs repository:
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/log/?h=iomap-4.19-merge
Thanks,
Andreas
Andreas Gruenbacher (3):
gfs2: fallocate_chunk: Always initialize struct iomap
gfs2: Use iomap for stuffed direct I/O reads
gfs2: use iomap_readpage for blocksize == PAGE_SIZE
--
2.17.1
next reply other threads:[~2018-07-07 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 9:39 Andreas Gruenbacher [this message]
2018-07-07 9:39 ` [Cluster-devel] [PATCH 1/3] gfs2: fallocate_chunk: Always initialize struct iomap Andreas Gruenbacher
2018-07-07 9:39 ` [Cluster-devel] [PATCH 2/3] gfs2: Use iomap for stuffed direct I/O reads Andreas Gruenbacher
2018-07-07 9:39 ` [Cluster-devel] [PATCH 3/3] gfs2: use iomap_readpage for blocksize == PAGE_SIZE Andreas Gruenbacher
2018-07-09 12:47 ` [Cluster-devel] [PATCH 0/3] gfs2: More iomap enablement 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=20180707093904.23177-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
/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).