From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 2/2] f2fs: reduce memory footprint of ino management
Date: Fri, 21 Aug 2026 15:50:14 +0000 [thread overview]
Message-ID: <178732741463.1339488.679147412162451324.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260819013107.3542105-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 19 Aug 2026 09:31:07 +0800 you wrote:
> Currently, ino entries for APPEND_INO, UPDATE_INO, TRANS_DIR_INO, and
> XATTR_DIR_INO allocate a 'struct ino_entry' slab object and attach it to
> both a list and a radix tree solely for existence checks via
> f2fs_exist_written_data().
>
> Since these ino types only track binary existence status, we can embed
> the information directly into radix tree value entries as a bitmap:
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,2/2] f2fs: reduce memory footprint of ino management
https://git.kernel.org/jaegeuk/f2fs/c/9a9ee7408a1f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 2/2] f2fs: reduce memory footprint of ino management
Date: Fri, 21 Aug 2026 15:50:14 +0000 [thread overview]
Message-ID: <178732741463.1339488.679147412162451324.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260819013107.3542105-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 19 Aug 2026 09:31:07 +0800 you wrote:
> Currently, ino entries for APPEND_INO, UPDATE_INO, TRANS_DIR_INO, and
> XATTR_DIR_INO allocate a 'struct ino_entry' slab object and attach it to
> both a list and a radix tree solely for existence checks via
> f2fs_exist_written_data().
>
> Since these ino types only track binary existence status, we can embed
> the information directly into radix tree value entries as a bitmap:
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,2/2] f2fs: reduce memory footprint of ino management
https://git.kernel.org/jaegeuk/f2fs/c/9a9ee7408a1f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-08-21 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 1:31 [f2fs-dev] [PATCH v3 2/2] f2fs: reduce memory footprint of ino management Chao Yu via Linux-f2fs-devel
2026-08-19 1:31 ` Chao Yu
2026-08-21 15:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-08-21 15:50 ` [f2fs-dev] " patchwork-bot+f2fs
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=178732741463.1339488.679147412162451324.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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 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.