From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zhiguo Niu <niuzhiguo84@gmail.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v8 07/12] f2fs: cache: use node cache
Date: Thu, 17 Sep 2026 10:55:37 +0800 [thread overview]
Message-ID: <94731ef5-4c1b-4aed-9a03-ab63a4fc8a7c@kernel.org> (raw)
In-Reply-To: <CAHJ8P3+0jVMFp3YTse8fbUTSp+jjW+2czxp0NuD__sHG_7UNXQ@mail.gmail.com>
On 9/16/26 17:15, Zhiguo Niu wrote:
>> static void __submit_merged_write_cond(struct f2fs_sb_info *sbi,
>> struct inode *inode, struct folio *folio,
>> - nid_t ino, enum page_type type, bool writeback)
>> + bool writeback)
> Hi Chao,
> seems this function just only handle DATA type now, so can we rename
> it xxx_data_xxx for easy reading?
Zhiguo,
I rename it to __submit_merged_data_write_cond() for readability.
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-09-17 2:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 1:54 [f2fs-dev] [PATCH v8 00/12] f2fs: introduce metadata cache Chao Yu via Linux-f2fs-devel
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 01/12] f2fs: cache: implement " Chao Yu via Linux-f2fs-devel
2026-09-16 8:32 ` Zhiguo Niu
2026-09-16 17:53 ` Jaegeuk Kim via Linux-f2fs-devel
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 02/12] f2fs: cache: initialize meta cache Chao Yu via Linux-f2fs-devel
2026-09-16 8:37 ` Zhiguo Niu
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 03/12] f2fs: cache: introduce shrinker Chao Yu via Linux-f2fs-devel
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 04/12] f2fs: cache: introduce writeback thread Chao Yu via Linux-f2fs-devel
2026-09-16 8:36 ` Zhiguo Niu
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 05/12] f2fs: cache: use meta cache Chao Yu via Linux-f2fs-devel
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 06/12] f2fs: cache: initialize node cache Chao Yu via Linux-f2fs-devel
2026-09-16 8:46 ` Zhiguo Niu
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 07/12] f2fs: cache: use " Chao Yu via Linux-f2fs-devel
2026-09-16 9:15 ` Zhiguo Niu
2026-09-16 17:01 ` Jaegeuk Kim via Linux-f2fs-devel
2026-09-17 2:55 ` Chao Yu via Linux-f2fs-devel [this message]
2026-09-17 5:55 ` Zhiguo Niu
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 08/12] f2fs: cache: initialize compress cache Chao Yu via Linux-f2fs-devel
2026-09-16 9:08 ` Zhiguo Niu
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 09/12] f2fs: cache: use " Chao Yu via Linux-f2fs-devel
2026-09-16 9:37 ` Zhiguo Niu
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 10/12] f2fs: cache: support fault injection Chao Yu via Linux-f2fs-devel
2026-09-16 8:35 ` Zhiguo Niu
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 11/12] f2fs: cache: introduce tracepoints Chao Yu via Linux-f2fs-devel
2026-09-16 8:34 ` Zhiguo Niu
2026-09-16 1:54 ` [f2fs-dev] [PATCH v8 12/12] f2fs: cache: show per-cache usage in debugfs Chao Yu via Linux-f2fs-devel
2026-09-16 9:39 ` Zhiguo Niu
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=94731ef5-4c1b-4aed-9a03-ab63a4fc8a7c@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@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.