From: patchwork-bot+f2fs@kernel.org
To: Sunmin Jeong <s_min.jeong@samsung.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, daehojeong@google.com,
stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net,
sj1557.seo@samsung.com
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: use meta inode for GC of atomic file
Date: Mon, 15 Jul 2024 14:40:32 +0000 [thread overview]
Message-ID: <172105443200.17443.3328341243004034413.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240710115117.61255-1-s_min.jeong@samsung.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 10 Jul 2024 20:51:17 +0900 you wrote:
> The page cache of the atomic file keeps new data pages which will be
> stored in the COW file. It can also keep old data pages when GCing the
> atomic file. In this case, new data can be overwritten by old data if a
> GC thread sets the old data page as dirty after new data page was
> evicted.
>
> Also, since all writes to the atomic file are redirected to COW inodes,
> GC for the atomic file is not working well as below.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,1/2] f2fs: use meta inode for GC of atomic file
https://git.kernel.org/jaegeuk/f2fs/c/b40a2b003709
- [f2fs-dev,v3,2/2] f2fs: use meta inode for GC of COW file
https://git.kernel.org/jaegeuk/f2fs/c/f18d00769336
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-15 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240710115137epcas1p2ee192f1264c9570c416c706ffa7c23e8@epcas1p2.samsung.com>
2024-07-10 11:51 ` [PATCH v3 1/2] f2fs: use meta inode for GC of atomic file Sunmin Jeong
2024-07-15 14:40 ` patchwork-bot+f2fs [this message]
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=172105443200.17443.3328341243004034413.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=s_min.jeong@samsung.com \
--cc=sj1557.seo@samsung.com \
--cc=stable@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