Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaeg...@kernel.org>:
On Sun, 10 Dec 2023 17:20:35 +0800 you wrote:
> Commit 3c6c2bebef79 ("f2fs: avoid punch_hole overhead when releasing
> volatile data") introduced FI_FIRST_BLOCK_WRITTEN as below reason:
>
> This patch is to avoid some punch_hole overhead when releasing volatile
> data. If volatile data was not written yet, we just can make the first
> page as zero.
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/6] f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN
https://git.kernel.org/jaegeuk/f2fs/c/a53936361330
- [f2fs-dev,2/6] f2fs: delete obsolete FI_DROP_CACHE
https://git.kernel.org/jaegeuk/f2fs/c/bb6e1c8fa5b9
- [f2fs-dev,3/6] f2fs: introduce get_dnode_addr() to clean up codes
https://git.kernel.org/jaegeuk/f2fs/c/2020cd48e41c
- [f2fs-dev,4/6] f2fs: update blkaddr in __set_data_blkaddr() for cleanup
https://git.kernel.org/jaegeuk/f2fs/c/59d0d4c3eae0
- [f2fs-dev,5/6] f2fs: introduce f2fs_invalidate_internal_cache() for cleanup
https://git.kernel.org/jaegeuk/f2fs/c/4e4f1eb9949b
- [f2fs-dev,6/6] f2fs: add tracepoint for f2fs_vm_page_mkwrite()
https://git.kernel.org/jaegeuk/f2fs/c/87f3afd366f7
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
