From: Chao Yu <chao@kernel.org>
To: Yi Sun <yi.sun@unisoc.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, Ke.Wang@unisoc.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, Hao_hao.Wang@unisoc.com,
niuzhiguo84@gmail.com, zhiguo.niu@unisoc.com
Subject: Re: [PATCH] f2fs: Clean up the loop outside of f2fs_invalidate_blocks()
Date: Wed, 22 Jan 2025 15:59:55 +0800 [thread overview]
Message-ID: <63bb967d-5464-4d6b-9daa-7059608bfba2@kernel.org> (raw)
In-Reply-To: <20250113014702.2312729-1-yi.sun@unisoc.com>
On 1/13/25 09:47, Yi Sun wrote:
> Now f2fs_invalidate_blocks() supports a continuous range of addresses,
> so the for loop can be omitted.
>
> Signed-off-by: Yi Sun <yi.sun@unisoc.com>
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
Actually, this can be merged into "f2fs: add parameter @len to
f2fs_invalidate_blocks()", but, anyway, I guess it's fine to merge it separately.
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
> ---
> fs/f2fs/file.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 9980d17ef9f5..4baafad7a00c 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -811,10 +811,8 @@ int f2fs_do_truncate_blocks(struct inode *inode, u64 from, bool lock)
> if (IS_DEVICE_ALIASING(inode)) {
> struct extent_tree *et = F2FS_I(inode)->extent_tree[EX_READ];
> struct extent_info ei = et->largest;
> - unsigned int i;
>
> - for (i = 0; i < ei.len; i++)
> - f2fs_invalidate_blocks(sbi, ei.blk + i, 1);
> + f2fs_invalidate_blocks(sbi, ei.blk, ei.len);
>
> dec_valid_block_count(sbi, inode, ei.len);
> f2fs_update_time(sbi, REQ_TIME);
next prev parent reply other threads:[~2025-01-22 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 1:47 [PATCH] f2fs: Clean up the loop outside of f2fs_invalidate_blocks() Yi Sun
2025-01-22 7:59 ` Chao Yu [this message]
2025-01-22 21:20 ` [f2fs-dev] " patchwork-bot+f2fs
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=63bb967d-5464-4d6b-9daa-7059608bfba2@kernel.org \
--to=chao@kernel.org \
--cc=Hao_hao.Wang@unisoc.com \
--cc=Ke.Wang@unisoc.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@gmail.com \
--cc=yi.sun@unisoc.com \
--cc=zhiguo.niu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox