linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-xfs <linux-xfs@vger.kernel.org>,
	Eric Sandeen <sandeen@sandeen.net>,
	agruenba@redhat.com, Christoph Hellwig <hch@infradead.org>
Subject: [GIT PULL] xfs: 4.19 merge, part 1
Date: Mon, 13 Aug 2018 07:51:40 -0700	[thread overview]
Message-ID: <20180813145140.GD11750@magnolia> (raw)

Hi Linus,

This is the first part of the XFS changes for 4.19.  Christoph and
Andreas coordinated some refactoring work on the iomap code in
preparation for removing buffer heads from XFS and porting gfs2 to
iomap.  I'm sending this small pull request ahead of the main XFS merge
to avoid holding up gfs2 unnecessarily.

--D

The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:

  Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git iomap-4.19-merge

for you to fetch changes up to 806a1477b10a153cd01ee7ccba8ca2492df3e0b2:

  iomap: add inline data support to iomap_readpage_actor (2018-07-03 09:07:47 -0700)

----------------------------------------------------------------
Andreas Gruenbacher (6):
      iomap: mark newly allocated buffer heads as new
      iomap: complete partial direct I/O writes synchronously
      iomap: generic inline data handling
      iomap: add private pointer to struct iomap
      iomap: support direct I/O to inline data
      iomap: add inline data support to iomap_readpage_actor

Christoph Hellwig (5):
      fs: factor out a __generic_write_end helper
      iomap: add a page_done callback
      iomap: add an iomap-based readpage and readpages implementation
      iomap: add initial support for writes without buffer heads
      iomap: refactor iomap_dio_actor

 fs/buffer.c           |  76 ++++----
 fs/internal.h         |   2 +
 fs/iomap.c            | 532 ++++++++++++++++++++++++++++++++++++++++++++------
 fs/xfs/xfs_iomap.c    |   6 +-
 include/linux/iomap.h |  16 ++
 5 files changed, 536 insertions(+), 96 deletions(-)

                 reply	other threads:[~2018-08-13 17:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180813145140.GD11750@magnolia \
    --to=djwong@kernel.org \
    --cc=agruenba@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=torvalds@linux-foundation.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).