From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: chao@kernel.org, Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH 16/20] f2fs: preserve inline data in subpage block mode
Date: Mon, 9 Nov 2026 11:18:06 +0800 [thread overview]
Message-ID: <610e99a6-c622-4a2e-9c6d-a57367994c42@kernel.org> (raw)
In-Reply-To: <20261102193952.3002018-17-daeho43@gmail.com>
On 11/3/26 03:39, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> A write to an inline inode converted it to a regular inode whenever the
> folio held multiple blocks, allocating a block even for small files.
> Convert only when the write goes beyond MAX_INLINE_DATA; otherwise read
> the inline data into the folio and write it back to the inode block in
> f2fs_write_cache_folios().
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
> fs/f2fs/data.c | 59 ++++++++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 50 insertions(+), 9 deletions(-)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 4e4d1b0d6004..a7cc7231b572 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -4732,6 +4732,21 @@ static int f2fs_write_cache_folios(struct address_space *mapping,
> }
> }
>
> + if (f2fs_has_inline_data(inode)) {
> + err = f2fs_write_inline_data(inode, folio);
> + if (!err) {
> + f2fs_ffs_clear_subrange_dirty_and_test(folio, 0,
> + folio_size(folio));
> + inode_sub_dirty_blocks(inode, f2fs_blocks_per_folio(sbi, folio));
> + goto retry_out;
> + }
> + if (err != -EAGAIN) {
IIUC, -EAGAIN should not happen here? because we only convert inline to non inline
inode after we hold folio lock and inode cache lock, since we have held folio lock,
so there is no way to convert?
Thanks,
> + folio_redirty_for_writepage(wbc, folio);
> + goto retry_out;
> + }
> + err = 0;
> + }
> +
> folio_start_writeback(folio);
>
> /*
> @@ -4913,8 +4928,7 @@ static int __f2fs_write_data_pages(struct address_space *mapping,
> account_writeback(inode, true);
>
> blk_start_plug(&plug);
> - if (f2fs_has_multiblock_folios(inode) &&
> - !f2fs_has_inline_data(inode))
> + if (f2fs_has_multiblock_folios(inode))
> ret = f2fs_write_cache_folios(mapping, wbc, io_type);
> else
> ret = f2fs_write_cache_pages(mapping, wbc, io_type);
> @@ -4981,6 +4995,16 @@ void f2fs_write_failed(struct inode *inode, loff_t to)
> }
> }
>
> +/* Fill @folio from the inline data for a write within the inline area */
> +static void prepare_inline_write_begin(struct inode *inode,
> + struct folio *folio, struct f2fs_cached_block *ientry)
> +{
> + f2fs_do_read_inline_data(folio, ientry);
> + set_inode_flag(inode, FI_DATA_EXIST);
> + if (inode->i_nlink)
> + f2fs_cache_set_inline(ientry);
> +}
> +
> static int prepare_write_begin(struct f2fs_sb_info *sbi,
> struct folio *folio, loff_t pos, unsigned int len,
> block_t *blk_addr, bool *node_changed)
> @@ -5034,10 +5058,7 @@ static int prepare_write_begin(struct f2fs_sb_info *sbi,
>
> if (f2fs_has_inline_data(inode)) {
> if (pos + len <= MAX_INLINE_DATA(inode)) {
> - f2fs_do_read_inline_data(folio, ientry);
> - set_inode_flag(inode, FI_DATA_EXIST);
> - if (inode->i_nlink)
> - f2fs_cache_set_inline(ientry);
> + prepare_inline_write_begin(inode, folio, ientry);
> goto out;
> }
> err = f2fs_convert_inline_folio(&dn, folio);
> @@ -5454,7 +5475,8 @@ static int f2fs_write_begin(const struct kiocb *iocb,
> * and #0 page. The locking rule for inline_data conversion should be:
> * folio_lock(folio #0) -> folio_lock(inode_page)
> */
> - if (index != 0 || f2fs_has_subpage_blocks(sbi)) {
> + if (index != 0 || (f2fs_has_subpage_blocks(sbi) &&
> + pos + len > MAX_INLINE_DATA(inode))) {
> err = f2fs_convert_inline_inode(inode);
> if (err)
> goto fail;
> @@ -5510,6 +5532,23 @@ static int f2fs_write_begin(const struct kiocb *iocb,
> blen = min_t(unsigned int, len,
> folio_size(folio) - offset_in_folio(folio, pos));
>
> + if (f2fs_has_inline_data(inode) && f2fs_is_multiblock_folio(sbi, folio)) {
> + struct f2fs_lock_context lc;
> + struct f2fs_cached_block *ientry;
> +
> + f2fs_map_lock(sbi, &lc, F2FS_GET_BLOCK_PRE_AIO);
> + ientry = f2fs_get_inode_cache(sbi, inode->i_ino);
> + if (IS_ERR(ientry)) {
> + f2fs_map_unlock(sbi, &lc, F2FS_GET_BLOCK_PRE_AIO);
> + err = PTR_ERR(ientry);
> + goto put_folio;
> + }
> + prepare_inline_write_begin(inode, folio, ientry);
> + f2fs_put_cache(ientry, true);
> + f2fs_map_unlock(sbi, &lc, F2FS_GET_BLOCK_PRE_AIO);
> + return 0;
> + }
> +
> /*
> * Flush the cached IO of this folio before touching it, especially
> * for the large folio prepare below which reads and updates subpage
> @@ -5618,7 +5657,8 @@ static int f2fs_write_end(const struct kiocb *iocb,
> if (!folio_test_uptodate(folio)) {
> if (unlikely(copied != len)) {
> copied = 0;
> - } else if (f2fs_is_multiblock_folio(F2FS_I_SB(inode), folio)) {
> + } else if (f2fs_is_multiblock_folio(F2FS_I_SB(inode), folio) &&
> + !f2fs_has_inline_data(inode)) {
> f2fs_ffs_mark_subrange_uptodate(folio,
> offset_in_folio(folio, pos), len);
> } else {
> @@ -5645,7 +5685,8 @@ static int f2fs_write_end(const struct kiocb *iocb,
> if (!copied)
> goto unlock_out;
>
> - if (f2fs_is_multiblock_folio(F2FS_I_SB(inode), folio))
> + if (f2fs_is_multiblock_folio(F2FS_I_SB(inode), folio) &&
> + !f2fs_has_inline_data(inode))
> f2fs_ffs_mark_subrange_dirty(folio, offset_in_folio(folio, pos),
> copied);
> folio_mark_dirty(folio);
next prev parent reply other threads:[~2026-11-09 3:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 19:39 [PATCH 00/20] f2fs: support block size smaller than PAGE_SIZE Daeho Jeong
2026-11-02 19:39 ` [PATCH 01/20] f2fs: use block-based index and size calculations in remaining paths Daeho Jeong
2026-11-03 7:04 ` [f2fs-dev] " Chao Yu
2026-11-02 19:39 ` [PATCH 02/20] f2fs: support subpage block size superblock and mount Daeho Jeong
2026-11-03 9:26 ` [f2fs-dev] " Chao Yu
2026-11-02 19:39 ` [PATCH 03/20] f2fs: extend f2fs_folio_state for subpage blocks Daeho Jeong
2026-11-04 9:19 ` [f2fs-dev] " Chao Yu
2026-11-06 20:53 ` Daeho Jeong
2026-11-02 19:39 ` [PATCH 04/20] f2fs: support subpage blocks in directory operations Daeho Jeong
2026-11-04 11:13 ` [f2fs-dev] " Chao Yu
2026-11-02 19:39 ` [PATCH 05/20] f2fs: convert inode dirty page counters to dirty block counters Daeho Jeong
2026-11-04 11:24 ` [f2fs-dev] " Chao Yu
2026-11-06 21:29 ` Daeho Jeong
2026-11-02 19:39 ` [PATCH 06/20] f2fs: support subpage blocks in data read path and GC Daeho Jeong
2026-11-05 7:55 ` [f2fs-dev] " Chao Yu
2026-11-02 19:39 ` [PATCH 07/20] f2fs: support subpage blocks in data write path and writeback Daeho Jeong
2026-11-06 2:52 ` [f2fs-dev] " Chao Yu
2026-11-07 23:14 ` Daeho Jeong
2026-11-02 19:39 ` [PATCH 08/20] f2fs: adapt range operations and mmap for subpage blocks Daeho Jeong
2026-11-06 3:54 ` [f2fs-dev] " Chao Yu
2026-11-07 23:24 ` Daeho Jeong
2026-11-02 19:39 ` [PATCH 09/20] f2fs: support subpage blocks in pinned files Daeho Jeong
2026-11-02 19:39 ` [PATCH 10/20] f2fs: support subpage blocks in collapse and insert range Daeho Jeong
2026-11-02 19:39 ` [PATCH 11/20] f2fs: support subpage blocks in move range Daeho Jeong
2026-11-02 19:39 ` [PATCH 12/20] f2fs: support subpage blocks in defragmentation Daeho Jeong
2026-11-02 19:39 ` [PATCH 13/20] f2fs: support subpage blocks in swapfile activation Daeho Jeong
2026-11-02 19:39 ` [PATCH 14/20] f2fs: support subpage blocks in fs-verity enablement Daeho Jeong
2026-11-02 19:39 ` [PATCH 15/20] f2fs: support subpage blocks in atomic writes Daeho Jeong
2026-11-09 2:56 ` [f2fs-dev] " Chao Yu
2026-11-02 19:39 ` [PATCH 16/20] f2fs: preserve inline data in subpage block mode Daeho Jeong
2026-11-09 3:18 ` Chao Yu [this message]
2026-11-02 19:39 ` [PATCH 17/20] f2fs: support subpage blocks in online resize Daeho Jeong
2026-11-02 19:39 ` [PATCH 18/20] f2fs: support subpage blocks in compression Daeho Jeong
2026-11-02 19:39 ` [PATCH 19/20] f2fs: count compress cache entries in pages for its memory limit Daeho Jeong
2026-11-02 19:39 ` [PATCH 20/20] f2fs: enable subpage block size support Daeho Jeong
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=610e99a6-c622-4a2e-9c6d-a57367994c42@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®