From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Wenjie Qi <qwjhust@gmail.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net, qiwenjie@xiaomi.com,
linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v5 04/12] f2fs: cache: introduce writeback thread
Date: Wed, 2 Sep 2026 20:22:15 +0800 [thread overview]
Message-ID: <46ee7fba-6a20-473c-b87d-856fa4ce1865@kernel.org> (raw)
In-Reply-To: <20260902115636.691796-1-qiwenjie@xiaomi.com>
Wenjie,
Thanks for the review, I've fixed all issues in 04/12 and 09/12 patch in
https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/log/?h=feature/cache,
please take a look.
On 9/2/26 19:56, Wenjie Qi wrote:
> Hi Chao,
>
>> static int f2fs_cache_writeback_kthread(void *data)
>> {
>> unsigned int interval = cache_thread->cache_wb_interval;
>> }
>
> and startup initializes the field after `kthread_run()`:
>
>> task = kthread_run(f2fs_cache_writeback_kthread, sbi, "%s", name);
>> if (IS_ERR(task))
>> return PTR_ERR(task);
>>
>> cache_thread->cache_wb_task = task;
>> cache_thread->cache_wb_interval = DEF_DIRTY_CACHE_TIMEOUT;
>
> `kthread_run()` wakes the new thread before returning, while
> `cache_wb_interval` is initially zero. The worker copies the field only
> once, and the sysfs store later updates the field rather than the local
> `interval`.
>
> Can the worker observe zero at startup, and can a later
> `cache_wb_interval` write change the interval used by that worker?
_______________________________________________
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-09-02 12:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 9:22 [f2fs-dev] [PATCH v5 00/12] f2fs: introduce metadata cache Chao Yu via Linux-f2fs-devel
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 01/12] f2fs: cache: implement " Chao Yu via Linux-f2fs-devel
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 02/12] f2fs: cache: initialize meta cache Chao Yu via Linux-f2fs-devel
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 03/12] f2fs: cache: introduce shrinker Chao Yu via Linux-f2fs-devel
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 04/12] f2fs: cache: introduce writeback thread Chao Yu via Linux-f2fs-devel
2026-09-02 11:56 ` Wenjie Qi
2026-09-02 12:22 ` Chao Yu via Linux-f2fs-devel [this message]
2026-09-02 11:57 ` Wenjie Qi
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 05/12] f2fs: cache: use meta cache Chao Yu via Linux-f2fs-devel
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 06/12] f2fs: cache: initialize node cache Chao Yu via Linux-f2fs-devel
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 07/12] f2fs: cache: use " Chao Yu via Linux-f2fs-devel
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 08/12] f2fs: cache: initialize compress cache Chao Yu via Linux-f2fs-devel
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 09/12] f2fs: cache: use " Chao Yu via Linux-f2fs-devel
2026-09-02 11:58 ` Wenjie Qi
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 10/12] f2fs: cache: support fault injection Chao Yu via Linux-f2fs-devel
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 11/12] f2fs: cache: introduce tracepoints Chao Yu via Linux-f2fs-devel
2026-08-31 9:22 ` [f2fs-dev] [PATCH v5 12/12] f2fs: cache: show per-cache usage in debugfs Chao Yu 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=46ee7fba-6a20-473c-b87d-856fa4ce1865@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiwenjie@xiaomi.com \
--cc=qwjhust@gmail.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.