From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, qiwenjie@xiaomi.com,
linux-f2fs-devel@lists.sourceforge.net, daehojeong@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v3 3/5] f2fs: cache: wake up f2fs_writeback when exceeding threshold
Date: Tue, 13 Oct 2026 22:30:38 +0000 [thread overview]
Message-ID: <179193063801.1493834.11114382446696553394.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261012091737.308136-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 12 Oct 2026 09:17:37 +0000 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> This patch introduces cache_wb_dirty_threshold and cache_wb_total_threshold
> sysfs nodes under /sys/fs/f2fs/<disk>/, and wakes up the f2fs_writeback
> kthread when dirty meta/node caches exceed cache_wb_dirty_threshold and
> total cached entries exceed cache_wb_total_threshold; a zero threshold
> disables the corresponding check. By default, cache_wb_dirty_threshold is
> 8192 and cache_wb_total_threshold is 0.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,3/5] f2fs: cache: wake up f2fs_writeback when exceeding threshold
https://git.kernel.org/jaegeuk/f2fs/c/eeadc4807c95
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
prev parent reply other threads:[~2026-10-13 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 9:17 [f2fs-dev] [PATCH v3 3/5] f2fs: cache: wake up f2fs_writeback when exceeding threshold Chao Yu via Linux-f2fs-devel
2026-10-12 9:52 ` Wenjie Qi
2026-10-13 22:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=179193063801.1493834.11114382446696553394.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=qiwenjie@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 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.