cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/7] lseek SEEK_HOLE / SEEK_DATA via iomap
Date: Fri, 16 Jun 2017 16:51:13 +0200	[thread overview]
Message-ID: <1497624680-16685-1-git-send-email-agruenba@redhat.com> (raw)

Here's an updated patch queue that implements iomap in gfs2 and switches gfs2
fiemap over to use iomap.  Following that is lseek SEEK_HOLE and SEEK_DATA
support for gfs2 and xfs.  Finally, xfs's internal use of lseek SEEK_HOLE /
SEEK_DATA is converted to iomap.

With the approach taken by this patch queue, filesystems that support iomap
still need to implement fiemap and lseek SEEK_HOLE / SEEK_DATA separately.
Those implementations will all be identical except for the filesystem specific
locking / unlocking code at the beginning / end of the operations.

Wouldn't it make sense to add iomap_lock and iomap_unlock operations, expose
the iomap ops at the vfs layer, and implement fiemap and lseek SEEK_HOLE /
SEEK_DATA generically in a next step?

Thanks,
Andreas


Andreas Gruenbacher (4):
  vfs: Add iomap_seek_hole_data helper
  gfs2: Implement lseek SEEK_HOLE / SEEK_DATA via iomap
  xfs: Switch to iomap for lseek SEEK_HOLE / SEEK_DATA
  xfs: Switch to iomap for seeking in quota files

Bob Peterson (3):
  GFS2: Make height info part of metapath
  GFS2: Implement iomap for block_map
  GFS2: Switch fiemap implementation to use iomap

 fs/gfs2/Kconfig       |   1 +
 fs/gfs2/bmap.c        | 288 ++++++++++++++++++++++++++++++------------
 fs/gfs2/bmap.h        |   4 +
 fs/gfs2/file.c        |  14 ++-
 fs/gfs2/inode.c       |  54 ++++++--
 fs/gfs2/inode.h       |   1 +
 fs/gfs2/trace_gfs2.h  |  65 ++++++++++
 fs/iomap.c            |  81 ++++++++++++
 fs/xfs/xfs_dquot.c    |   5 +-
 fs/xfs/xfs_file.c     | 337 +-------------------------------------------------
 fs/xfs/xfs_inode.h    |   2 -
 include/linux/iomap.h |   9 +-
 12 files changed, 429 insertions(+), 432 deletions(-)

-- 
2.7.5



             reply	other threads:[~2017-06-16 14:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16 14:51 Andreas Gruenbacher [this message]
2017-06-16 14:51 ` [Cluster-devel] [PATCH 1/7] GFS2: Make height info part of metapath Andreas Gruenbacher
2017-06-16 14:51 ` [Cluster-devel] [PATCH 2/7] GFS2: Implement iomap for block_map Andreas Gruenbacher
2017-06-16 14:51 ` [Cluster-devel] [PATCH 3/7] GFS2: Switch fiemap implementation to use iomap Andreas Gruenbacher
2017-06-16 14:51 ` [Cluster-devel] [PATCH 4/7] vfs: Add iomap_seek_hole_data helper Andreas Gruenbacher
2017-06-19 17:32   ` Darrick J. Wong
2017-06-16 14:51 ` [Cluster-devel] [PATCH 5/7] gfs2: Implement lseek SEEK_HOLE / SEEK_DATA via iomap Andreas Gruenbacher
2017-06-16 14:51 ` [Cluster-devel] [PATCH 6/7] xfs: Switch to iomap for lseek SEEK_HOLE / SEEK_DATA Andreas Gruenbacher
2017-06-17 23:57   ` Dave Chinner
2017-06-19 22:16     ` Andreas Gruenbacher
2017-06-16 14:51 ` [Cluster-devel] [PATCH 7/7] xfs: Switch to iomap for seeking in quota files Andreas Gruenbacher
2017-06-16 15:30   ` Darrick J. Wong
2017-06-20  6:31     ` Christoph Hellwig

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=1497624680-16685-1-git-send-email-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).