Linux-f2fs-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 v2 07/12] f2fs: cache: use node cache
Date: Tue, 25 Aug 2026 14:40:14 +0800	[thread overview]
Message-ID: <f9369204-aad5-499c-bad5-fb268ee0c2c5@kernel.org> (raw)
In-Reply-To: <20260825054331.400340-1-qiwenjie@xiaomi.com>

On 8/25/26 13:43, Wenjie Qi wrote:
> Hi Chao,
> 
>> if (!f2fs_clear_cache_dirty(entry))
>> 	goto continue_unlock;
>>
>> if (!__write_node_cache(entry, ...))
>> 	...
> 
> and in `__write_node_cache()`:
> 
>> if (unlikely(ni.blk_addr == NULL_ADDR)) {
>> 	f2fs_cache_clear_uptodate(entry);
>> 	dec_page_count(sbi, F2FS_DIRTY_NODES);
>> 	...
>> 	return true;
>> }
> 
> `f2fs_clear_cache_dirty()` clears the entry state bit but leaves the DIRTY
> radix tag for the writeback transition.  The `NULL_ADDR` return does not reach
> that transition, while it clears UPTODATE and decrements the dirty-node count.
> 
> What clears the DIRTY radix tag when this already-truncated path returns?

Hmm, Actually, I don't change the logic here, just change the API, I can take
a look original logic a bit later.

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2026-08-25  6:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 13:47 [f2fs-dev] [PATCH] f2fs: introduce metadata cache Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 01/12] f2fs: cache: implement " Chao Yu via Linux-f2fs-devel
2026-08-25  5:39   ` Wenjie Qi
2026-08-25  6:35     ` Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 02/12] f2fs: cache: initialize meta cache Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 03/12] f2fs: cache: introduce shrinker Chao Yu via Linux-f2fs-devel
2026-08-25  5:42   ` Wenjie Qi
2026-08-25  6:36     ` Chao Yu via Linux-f2fs-devel
2026-08-25  5:42   ` Wenjie Qi
2026-08-25  6:37     ` Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 04/12] f2fs: cache: introduce writeback thread Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 05/12] f2fs: cache: use meta cache Chao Yu via Linux-f2fs-devel
2026-08-25  5:42   ` Wenjie Qi
2026-08-25  6:37     ` Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 06/12] f2fs: cache: initialize node cache Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 07/12] f2fs: cache: use " Chao Yu via Linux-f2fs-devel
2026-08-25  5:43   ` Wenjie Qi
2026-08-25  6:38     ` Chao Yu via Linux-f2fs-devel
2026-08-25  5:43   ` Wenjie Qi
2026-08-25  6:40     ` Chao Yu via Linux-f2fs-devel [this message]
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 08/12] f2fs: cache: initialize compress cache Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 09/12] f2fs: cache: use " Chao Yu via Linux-f2fs-devel
2026-08-25  5:43   ` Wenjie Qi
2026-08-25  6:42     ` Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 10/12] f2fs: cache: support fault injection Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 11/12] f2fs: cache: introduce tracepoints Chao Yu via Linux-f2fs-devel
2026-08-24 13:47 ` [f2fs-dev] [PATCH v2 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=f9369204-aad5-499c-bad5-fb268ee0c2c5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox