linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
	linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: [PATCH v3 0/5] lseek SEEK_HOLE / SEEK_DATA fix and switch to iomap
Date: Mon, 26 Jun 2017 16:25:13 +0200	[thread overview]
Message-ID: <1498487118-6564-1-git-send-email-agruenba@redhat.com> (raw)

Here is an updated version of the lseek and iomap patches.  Changes:

 * Some cleanups to iomap_seek_{hole,data}_actor.

 * GFS2 patches omitted for now; those can be discussed later.

 * Per request, lseek and iomap patches posted in a single patch queue.

Thanks,
Andreas

Andreas Gruenbacher (5):
  vfs: Add page_cache_seek_hole_data helper
  ext4: Switch to page_cache_seek_hole_data
  xfs: Switch to page_cache_seek_hole_data
  vfs: Add iomap_seek_hole_data helper
  xfs: Switch to iomap for SEEK_HOLE / SEEK_DATA

 fs/buffer.c                 | 125 +++++++++++++++++++++++++
 fs/ext4/file.c              | 144 +++--------------------------
 fs/iomap.c                  |  91 ++++++++++++++++++
 fs/xfs/xfs_file.c           | 218 +++-----------------------------------------
 include/linux/buffer_head.h |   2 +
 include/linux/iomap.h       |   3 +
 6 files changed, 248 insertions(+), 335 deletions(-)

-- 
2.7.5

             reply	other threads:[~2017-06-26 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 14:25 Andreas Gruenbacher [this message]
2017-06-26 14:25 ` [PATCH v3 1/5] vfs: Add page_cache_seek_hole_data helper Andreas Gruenbacher
2017-06-26 14:25 ` [PATCH v3 2/5] ext4: Switch to page_cache_seek_hole_data Andreas Gruenbacher
2017-06-26 14:25 ` [PATCH v3 3/5] xfs: " Andreas Gruenbacher
2017-06-26 14:25 ` [PATCH v3 4/5] vfs: Add iomap_seek_hole_data helper Andreas Gruenbacher
2017-06-26 14:25 ` [PATCH v3 5/5] xfs: Switch to iomap for SEEK_HOLE / SEEK_DATA Andreas Gruenbacher
2017-06-27  0:34   ` Darrick J. Wong
2017-06-27 12:56     ` Dave Chinner

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=1498487118-6564-1-git-send-email-agruenba@redhat.com \
    --to=agruenba@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@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).