From: patchwork-bot+f2fs@kernel.org
To: patchwork-bot+f2fs--- via Linux-f2fs-devel
<linux-f2fs-devel@lists.sourceforge.net>
Cc: jaegeuk@kernel.org, chao@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v3 0/2] f2fs: modify the calculation method of mtime
Date: Mon, 28 Oct 2024 17:40:48 +0000 [thread overview]
Message-ID: <173013724899.126843.18304853477430411378.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1726653980-590956-1-git-send-email-liuderong@oppo.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 18 Sep 2024 18:06:18 +0800 you wrote:
> From: liuderong <liuderong@oppo.com>
>
> In cost-benefit GC algorithm, mtime will affect
> the selection of victim segment.For a large section,
> mtime should be the mean value of valid blocks,
> in order to select correct victim segment,
> it needs to modify the calculation method of mtime.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,1/2] f2fs: remove unused parameters
(no matching commit)
- [f2fs-dev,v3,2/2] f2fs: introduce f2fs_get_section_mtime
https://git.kernel.org/jaegeuk/f2fs/c/b19ee7272208
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-10-28 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 10:06 liuderong
2024-09-18 10:06 ` [PATCH v3 1/2] f2fs: remove unused parameters liuderong
2024-09-18 10:06 ` [PATCH v3 2/2] f2fs: introduce f2fs_get_section_mtime liuderong
2024-09-19 1:36 ` Chao Yu
2024-10-28 17: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=173013724899.126843.18304853477430411378.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome