From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Yi Sun <yi.sun@unisoc.com>, jaegeuk@kernel.org
Cc: ke.wang@unisoc.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, sunyibuaa@gmail.com,
hao_hao.wang@unisoc.com
Subject: Re: [f2fs-dev] [PATCH v2 3/5] f2fs: add parameter @len to f2fs_invalidate_internal_cache()
Date: Thu, 31 Oct 2024 15:27:09 +0800 [thread overview]
Message-ID: <cf81df94-3ff3-44b8-97ad-e68b6315fcdc@kernel.org> (raw)
In-Reply-To: <20241030103136.2874140-4-yi.sun@unisoc.com>
On 2024/10/30 18:31, Yi Sun wrote:
> New function can process some consecutive blocks at a time.
>
> Signed-off-by: Yi Sun <yi.sun@unisoc.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
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Yi Sun <yi.sun@unisoc.com>, jaegeuk@kernel.org
Cc: Chao Yu <chao@kernel.org>,
sunyibuaa@gmail.com, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, niuzhiguo84@gmail.com,
hao_hao.wang@unisoc.com, ke.wang@unisoc.com
Subject: Re: [PATCH v2 3/5] f2fs: add parameter @len to f2fs_invalidate_internal_cache()
Date: Thu, 31 Oct 2024 15:27:09 +0800 [thread overview]
Message-ID: <cf81df94-3ff3-44b8-97ad-e68b6315fcdc@kernel.org> (raw)
In-Reply-To: <20241030103136.2874140-4-yi.sun@unisoc.com>
On 2024/10/30 18:31, Yi Sun wrote:
> New function can process some consecutive blocks at a time.
>
> Signed-off-by: Yi Sun <yi.sun@unisoc.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2024-10-31 7:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 10:31 [f2fs-dev] [PATCH v2 0/5] Speed up f2fs truncate Yi Sun
2024-10-30 10:31 ` Yi Sun
2024-10-30 10:31 ` [f2fs-dev] [PATCH v2 1/5] f2fs: blocks need to belong to the same segment when using update_sit_entry() Yi Sun
2024-10-30 10:31 ` Yi Sun
2024-10-31 7:19 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2024-10-31 7:19 ` Chao Yu
2024-10-30 10:31 ` [f2fs-dev] [PATCH v2 2/5] f2fs: expand f2fs_invalidate_compress_page() to f2fs_invalidate_compress_pages_range() Yi Sun
2024-10-30 10:31 ` Yi Sun
2024-10-31 7:26 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2024-10-31 7:26 ` Chao Yu
2024-10-31 9:02 ` [f2fs-dev] " yi sun
2024-10-31 9:02 ` yi sun
2024-10-30 10:31 ` [f2fs-dev] [PATCH v2 3/5] f2fs: add parameter @len to f2fs_invalidate_internal_cache() Yi Sun
2024-10-30 10:31 ` Yi Sun
2024-10-31 7:27 ` Chao Yu via Linux-f2fs-devel [this message]
2024-10-31 7:27 ` Chao Yu
2024-10-30 10:31 ` [f2fs-dev] [PATCH v2 4/5] f2fs: add parameter @len to f2fs_invalidate_blocks() Yi Sun
2024-10-30 10:31 ` Yi Sun
2024-10-30 17:00 ` [f2fs-dev] " Daeho Jeong
2024-10-30 17:00 ` Daeho Jeong
2024-10-31 3:00 ` yi sun
2024-10-31 3:00 ` yi sun
2024-10-31 9:10 ` Zhiguo Niu
2024-10-31 9:10 ` Zhiguo Niu
2024-10-31 10:51 ` yi sun
2024-10-31 10:51 ` yi sun
2024-11-01 3:39 ` yi sun
2024-11-01 3:39 ` yi sun
2024-10-30 10:31 ` [f2fs-dev] [PATCH v2 5/5] f2fs: Optimize f2fs_truncate_data_blocks_range() Yi Sun
2024-10-30 10:31 ` Yi Sun
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=cf81df94-3ff3-44b8-97ad-e68b6315fcdc@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=hao_hao.wang@unisoc.com \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sunyibuaa@gmail.com \
--cc=yi.sun@unisoc.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.