From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>
Cc: "Matthew Wilcox \(Oracle\)" <willy@infradead.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 00/11] f2fs folio patches
Date: Thu, 28 Nov 2024 04:58:15 +0000 [thread overview]
Message-ID: <20241128045828.527559-1-willy@infradead.org> (raw)
This round of f2fs patches accomplishes two things:
- Removal of all references to page->index in f2fs. I'm looking to
finish this conversion in the January merge window.
- Removal of all calls to page_file_mapping() and folio_file_mapping()
I have only compile-tested these patches.
Matthew Wilcox (Oracle) (11):
f2fs: Use a folio in f2fs_all_cluster_page_ready()
f2fs: Use a folio in f2fs_compress_write_end()
f2fs: Use a folio in f2fs_truncate_partial_cluster()
f2fs: Use a folio in f2fs_write_compressed_pages()
f2fs: Convert submit tracepoints to take a folio
f2fs: Add F2FS_F_SB()
f2fs: Convert f2fs_finish_read_bio() to use folios
f2fs: Use a folio more in f2fs_submit_page_bio()
f2fs: Use a data folio in f2fs_submit_page_bio()
f2fs: Convert __read_io_type() to take a folio
f2fs: Remove calls to folio_file_mapping()
fs/f2fs/compress.c | 28 ++++++++++++--------
fs/f2fs/data.c | 53 +++++++++++++++----------------------
fs/f2fs/f2fs.h | 7 ++++-
fs/f2fs/inline.c | 2 +-
include/trace/events/f2fs.h | 39 +++++++++++++--------------
5 files changed, 65 insertions(+), 64 deletions(-)
--
2.45.2
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2024-11-28 5:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 4:58 Matthew Wilcox (Oracle) [this message]
2024-11-28 4:58 ` [f2fs-dev] [PATCH 01/11] f2fs: Use a folio in f2fs_all_cluster_page_ready() Matthew Wilcox (Oracle)
2024-11-28 4:58 ` [f2fs-dev] [PATCH 02/11] f2fs: Use a folio in f2fs_compress_write_end() Matthew Wilcox (Oracle)
2024-11-28 4:58 ` [f2fs-dev] [PATCH 03/11] f2fs: Use a folio in f2fs_truncate_partial_cluster() Matthew Wilcox (Oracle)
2024-11-28 4:58 ` [f2fs-dev] [PATCH 04/11] f2fs: Use a folio in f2fs_write_compressed_pages() Matthew Wilcox (Oracle)
2024-11-28 4:58 ` [f2fs-dev] [PATCH 05/11] f2fs: Convert submit tracepoints to take a folio Matthew Wilcox (Oracle)
2024-11-28 4:58 ` [f2fs-dev] [PATCH 06/11] f2fs: Add F2FS_F_SB() Matthew Wilcox (Oracle)
2024-11-28 4:58 ` [f2fs-dev] [PATCH 07/11] f2fs: Convert f2fs_finish_read_bio() to use folios Matthew Wilcox (Oracle)
2024-11-28 4:58 ` [f2fs-dev] [PATCH 08/11] f2fs: Use a folio more in f2fs_submit_page_bio() Matthew Wilcox (Oracle)
2024-11-28 4:58 ` [f2fs-dev] [PATCH 09/11] f2fs: Use a data folio " Matthew Wilcox (Oracle)
2024-11-28 4:58 ` [f2fs-dev] [PATCH 10/11] f2fs: Convert __read_io_type() to take a folio Matthew Wilcox (Oracle)
2024-11-28 4:58 ` [f2fs-dev] [PATCH 11/11] f2fs: Remove calls to folio_file_mapping() Matthew Wilcox (Oracle)
2024-12-16 13:59 ` [f2fs-dev] [PATCH 00/11] f2fs folio patches Matthew Wilcox
2024-12-16 16:11 ` Jaegeuk Kim via Linux-f2fs-devel
2024-12-16 14:39 ` Chao Yu via Linux-f2fs-devel
2024-12-16 16:40 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
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=20241128045828.527559-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).