From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
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: dump more information when checkpoint was blocked for long time
Date: Fri, 15 Aug 2025 16:40:22 +0000 [thread overview]
Message-ID: <175527602223.1161945.8969283986568227588.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250731053405.1127197-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 31 Jul 2025 13:34:04 +0800 you wrote:
> generic/299 w/ mode=lfs will cause long time latency of checkpoint,
> let's dump more information once we hit case.
>
> CP merge:
> - Queued : 0
> - Issued : 1
> - Total : 1
> - Cur time : 9765(ms)
> - Peak time : 9765(ms)
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: dump more information when checkpoint was blocked for long time
https://git.kernel.org/jaegeuk/f2fs/c/3fcf228b6494
- [f2fs-dev,2/2] f2fs: add time stats of checkpoint for debug
https://git.kernel.org/jaegeuk/f2fs/c/57e74035ad5e
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/2] f2fs: dump more information when checkpoint was blocked for long time
Date: Fri, 15 Aug 2025 16:40:22 +0000 [thread overview]
Message-ID: <175527602223.1161945.8969283986568227588.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250731053405.1127197-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 31 Jul 2025 13:34:04 +0800 you wrote:
> generic/299 w/ mode=lfs will cause long time latency of checkpoint,
> let's dump more information once we hit case.
>
> CP merge:
> - Queued : 0
> - Issued : 1
> - Total : 1
> - Cur time : 9765(ms)
> - Peak time : 9765(ms)
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: dump more information when checkpoint was blocked for long time
https://git.kernel.org/jaegeuk/f2fs/c/3fcf228b6494
- [f2fs-dev,2/2] f2fs: add time stats of checkpoint for debug
https://git.kernel.org/jaegeuk/f2fs/c/57e74035ad5e
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:[~2025-08-15 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 5:34 [f2fs-dev] [PATCH 1/2] f2fs: dump more information when checkpoint was blocked for long time Chao Yu via Linux-f2fs-devel
2025-07-31 5:34 ` Chao Yu
2025-07-31 5:34 ` [f2fs-dev] [PATCH 2/2] f2fs: add time stats of checkpoint for debug Chao Yu via Linux-f2fs-devel
2025-07-31 5:34 ` Chao Yu
2025-08-15 16:40 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-08-15 16:40 ` [f2fs-dev] [PATCH 1/2] f2fs: dump more information when checkpoint was blocked for long time 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=175527602223.1161945.8969283986568227588.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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.