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/2] f2fs: fix to account gc stats correctly
Date: Mon, 14 Aug 2023 20:50:22 +0000 [thread overview]
Message-ID: <169204622227.5033.2565918262411584066.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230808005949.1790839-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 8 Aug 2023 08:59:48 +0800 you wrote:
> As reported, status debugfs entry shows inconsistent GC stats as below:
>
> GC calls: 6008 (BG: 6161)
> - data segments : 3053 (BG: 3053)
> - node segments : 2955 (BG: 2955)
>
> Total GC calls is larger than BGGC calls, the reason is:
> - f2fs_stat_info.call_count accounts total migrated section count
> by f2fs_gc()
> - f2fs_stat_info.bg_gc accounts total call times of f2fs_gc() from
> background gc_thread
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: fix to account gc stats correctly
https://git.kernel.org/jaegeuk/f2fs/c/9bf1dcbdfdc8
- [f2fs-dev,2/2] f2fs: fix to account cp stats correctly
https://git.kernel.org/jaegeuk/f2fs/c/eb61c2cca2eb
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:[~2023-08-14 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 0:59 [PATCH 1/2] f2fs: fix to account gc stats correctly Chao Yu
2023-08-08 0:59 ` [PATCH 2/2] f2fs: fix to account cp " Chao Yu
2023-08-14 20:50 ` 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=169204622227.5033.2565918262411584066.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