From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Yongpeng Yang <monty_pavel@sina.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Yongpeng Yang <yangyongpeng@xiaomi.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/3] f2fs: add write latency stats for NAT and SIT blocks in f2fs_write_checkpoint
Date: Tue, 20 Jan 2026 20:27:12 +0800 [thread overview]
Message-ID: <329b019e-75ab-4d9b-a315-fa34efc77dea@kernel.org> (raw)
In-Reply-To: <20260113152138.15979-3-monty_pavel@sina.com>
On 1/13/2026 11:21 PM, Yongpeng Yang wrote:
> From: Yongpeng Yang <yangyongpeng@xiaomi.com>
>
> This patch adds separate write latency accounting for NAT and SIT blocks
> in f2fs_write_checkpoint().
>
> Signed-off-by: Yongpeng Yang <yangyongpeng@xiaomi.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-01-20 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 15:21 [f2fs-dev] [PATCH v2 0/3] f2fs: reduce checkpoint write latency under metadata-intensive workloads Yongpeng Yang
2026-01-13 15:21 ` [f2fs-dev] [PATCH v2 1/3] f2fs: add write latency stats for NAT and SIT blocks in f2fs_write_checkpoint Yongpeng Yang
2026-01-20 12:27 ` Chao Yu via Linux-f2fs-devel [this message]
2026-01-13 15:21 ` [f2fs-dev] [PATCH v2 2/3] f2fs: change size parameter of __has_cursum_space() to unsigned int Yongpeng Yang
2026-01-20 12:27 ` Chao Yu via Linux-f2fs-devel
2026-01-13 15:23 ` [f2fs-dev] [PATCH v2 3/3] f2fs: optimize NAT block loading during checkpoint write Yongpeng Yang
2026-01-20 12:32 ` Chao Yu via Linux-f2fs-devel
2026-01-22 23:50 ` [f2fs-dev] [PATCH v2 0/3] f2fs: reduce checkpoint write latency under metadata-intensive workloads patchwork-bot+f2fs--- via Linux-f2fs-devel
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=329b019e-75ab-4d9b-a315-fa34efc77dea@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=monty_pavel@sina.com \
--cc=yangyongpeng@xiaomi.com \
/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