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 1/6] f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN
Date: Thu, 14 Dec 2023 20:50:31 +0000 [thread overview]
Message-ID: <170258703198.30587.14823724778977847015.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231210092040.3374741-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@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
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 1/6] f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN
Date: Thu, 14 Dec 2023 20:50:31 +0000 [thread overview]
Message-ID: <170258703198.30587.14823724778977847015.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231210092040.3374741-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@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
next prev parent reply other threads:[~2023-12-14 20:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 9:20 [f2fs-dev] [PATCH 1/6] f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 9:20 ` [f2fs-dev] [PATCH 2/6] f2fs: delete obsolete FI_DROP_CACHE Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 9:20 ` [f2fs-dev] [PATCH 3/6] f2fs: introduce get_dnode_addr() to clean up codes Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 9:20 ` [f2fs-dev] [PATCH 4/6] f2fs: update blkaddr in __set_data_blkaddr() for cleanup Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 9:20 ` [f2fs-dev] [PATCH 5/6] f2fs: introduce f2fs_invalidate_internal_cache() " Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 9:20 ` [f2fs-dev] [PATCH 6/6] f2fs: add tracepoint for f2fs_vm_page_mkwrite() Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 19:10 ` kernel test robot
2023-12-14 20:50 ` patchwork-bot+f2fs [this message]
2023-12-14 20:50 ` [f2fs-dev] [PATCH 1/6] f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN 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=170258703198.30587.14823724778977847015.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--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 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.