From: Eric Biggers <ebiggers@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
Matthew Bobrowski <mbobrowski@mbobrowski.org>,
Satya Tangirala <satyaprateek2357@gmail.com>,
Changheun Lee <nanich.lee@samsung.com>
Subject: [f2fs-dev] [PATCH v2 0/2] f2fs: use iomap for direct I/O
Date: Fri, 23 Jul 2021 00:59:19 -0700 [thread overview]
Message-ID: <20210723075921.166705-1-ebiggers@kernel.org> (raw)
This series makes f2fs use the iomap direct I/O implementation instead
of the fs/direct-io.c one. In order to do this, it adds f2fs_iomap_ops,
since this is the first use of iomap in f2fs.
The iomap direct I/O implementation is more efficient than
fs/direct-io.c. Switching to iomap also avoids the need to add new
features and optimizations to the old implementation; e.g., see
https://lore.kernel.org/r/20200710053406.GA25530@infradead.org and
https://lore.kernel.org/r/YKJBWClI7sUeABDs@infradead.org.
Patch 1 adds f2fs_iomap_ops, and patch 2 switches direct I/O reads and
writes to iomap.
Careful review is appreciated, as I'm not an expert in all areas here.
This series applies to commit 0de0db9b033a of f2fs.git#dev
(https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/log/?h=dev).
Changed since v1:
- Dropped the preparatory cleanups/fixes for f2fs_file_write_iter(),
since they have been applied.
- Merged the last three patches into one.
- Implemented iomap_dio_ops::end_io() and switched to
__iomap_dio_rw() to simplify updating of f2fs's in-flight DIO
counters, as suggested by Christoph.
Eric Biggers (2):
f2fs: implement iomap operations
f2fs: use iomap for direct I/O
fs/f2fs/Kconfig | 1 +
fs/f2fs/data.c | 260 +++++++++---------------------------
fs/f2fs/f2fs.h | 22 +--
fs/f2fs/file.c | 346 ++++++++++++++++++++++++++++++++++++++++++------
4 files changed, 370 insertions(+), 259 deletions(-)
base-commit: 0de0db9b033af99f494c9ee4a2c9bac6456da1eb
--
2.32.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2021-07-23 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 7:59 Eric Biggers [this message]
2021-07-23 7:59 ` [f2fs-dev] [PATCH v2 1/2] f2fs: implement iomap operations Eric Biggers
2021-07-23 7:59 ` [f2fs-dev] [PATCH v2 2/2] f2fs: use iomap for direct I/O Eric Biggers
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=20210723075921.166705-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mbobrowski@mbobrowski.org \
--cc=nanich.lee@samsung.com \
--cc=satyaprateek2357@gmail.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).