From: Eric Biggers <ebiggers@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Gao Xiang <hsiangkao@linux.alibaba.com>,
Andreas Gruenbacher <agruenba@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: iomap 5.15 branch construction ...
Date: Mon, 2 Aug 2021 15:34:52 -0700 [thread overview]
Message-ID: <YQhzDPl13/Kl4JdQ@gmail.com> (raw)
In-Reply-To: <20210802221114.GG3601466@magnolia>
On Mon, Aug 02, 2021 at 03:11:14PM -0700, Darrick J. Wong wrote:
> 6. Earlier, Eric Biggers had a patchset that made some iomap changes
> ahead of porting f2fs to use directio. I /think/ those changes were
> dropped in the latest submission because the intended use of those
> changes (counters of the number of pages undergoing reads or writes,
> iirc?) has been replaced with something simpler. IOWs, f2fs doesn't
> need any iomap changes for 5.15, right?
Converting f2fs to use iomap for direct I/O doesn't require any iomap changes.
You might be referring to
https://lkml.kernel.org/r/20210604210908.2105870-7-satyat@google.com
("iomap: support direct I/O with fscrypt using blk-crypto"), which will be
needed to support direct I/O on encrypted files. Direct I/O support on
encrypted files will be a new feature, and it's being held up for other reasons.
So there's nothing for you to do for 5.15. (And separately, using iomap for
direct I/O in f2fs is being held up by existing f2fs direct I/O bugs.)
- Eric
next prev parent reply other threads:[~2021-08-02 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 22:11 iomap 5.15 branch construction Darrick J. Wong
2021-08-02 22:31 ` Andreas Gruenbacher
2021-08-02 22:34 ` Eric Biggers [this message]
2021-08-03 16:42 ` Darrick J. Wong
2021-08-03 0:21 ` Gao Xiang
2021-08-03 16:42 ` Darrick J. Wong
2021-08-03 3:21 ` Matthew Wilcox
2021-08-03 8:17 ` Christoph Hellwig
2021-08-03 8:40 ` 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=YQhzDPl13/Kl4JdQ@gmail.com \
--to=ebiggers@kernel.org \
--cc=agruenba@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.