From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org,
Andreas Gruenbacher <agruenba@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: iomap SEEK_HOLE / SEEK_DATA cleanups and generalization
Date: Wed, 30 May 2018 18:17:40 +0200 [thread overview]
Message-ID: <20180530161740.GA8385@lst.de> (raw)
In-Reply-To: <20180530160721.GB837@magnolia>
On Wed, May 30, 2018 at 09:07:21AM -0700, Darrick J. Wong wrote:
> On Wed, May 30, 2018 at 12:02:05PM +0200, Christoph Hellwig wrote:
> > Refactor the seek pagecache helpers to work independent of buffer_heads,
> > and clean up a few lose bits.
> >
> > This is needed for the small blocksize buffered I/O support in iomap.
>
> I added RVB tags to the previous version of this, but I guess they fell
> off? Have these three patches changed considerably since v3?
They haven't changed at all. So with the review from Andreas this might
be a good time to pull them in and get these patches off the backlog :)
next prev parent reply other threads:[~2018-05-30 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 10:02 iomap SEEK_HOLE / SEEK_DATA cleanups and generalization Christoph Hellwig
2018-05-30 10:02 ` [PATCH 1/3] fs: move page_cache_seek_hole_data to iomap.c Christoph Hellwig
2018-05-30 22:46 ` Dave Chinner
2018-05-30 10:02 ` [PATCH 2/3] fs: remove the buffer_unwritten check in page_seek_hole_data Christoph Hellwig
2018-05-30 22:47 ` Dave Chinner
2018-05-30 10:02 ` [PATCH 3/3] fs: use ->is_partially_uptodate in page_cache_seek_hole_data Christoph Hellwig
2018-05-30 13:48 ` Andreas Grünbacher
2018-05-30 23:00 ` Dave Chinner
2018-05-31 6:20 ` Christoph Hellwig
2018-05-30 16:07 ` iomap SEEK_HOLE / SEEK_DATA cleanups and generalization Darrick J. Wong
2018-05-30 16:17 ` Christoph Hellwig [this message]
2018-05-30 16:25 ` Darrick J. Wong
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=20180530161740.GA8385@lst.de \
--to=hch@lst.de \
--cc=agruenba@redhat.com \
--cc=darrick.wong@oracle.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).