[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173636163577.743062.15546397784828809130.git-patchwork-notify@kernel.org>
Date: Wed, 08 Jan 2025 18:40:35 +0000
From: patchwork-bot+f2fs@...nel.org
To: Yi Sun <yi.sun@...soc.com>
Cc: chao@...nel.org, jaegeuk@...nel.org, ke.wang@...soc.com,
linux-kernel@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
sunyibuaa@...il.com, Hao_hao.Wang@...soc.com
Subject: Re: [f2fs-dev] [PATCH v4 0/4] Speed up f2fs truncate
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@...nel.org>:
On Mon, 23 Dec 2024 16:10:40 +0800 you wrote:
> Deleting large files is time-consuming, and a large part
> of the time is spent in f2fs_invalidate_blocks()
> ->down_write(sit_info->sentry_lock) and up_write().
>
> If some blocks are continuous, we can process these blocks
> at the same time. This can reduce the number of calls to
> the down_write() and the up_write(), thereby improving the
> overall speed of doing truncate.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v4,1/4] f2fs: introduce update_sit_entry_for_release/alloc()
https://git.kernel.org/jaegeuk/f2fs/c/66baee2b886d
- [f2fs-dev,v4,2/4] f2fs: update_sit_entry_for_release() supports consecutive blocks.
https://git.kernel.org/jaegeuk/f2fs/c/81ffbd224e5f
- [f2fs-dev,v4,3/4] f2fs: add parameter @len to f2fs_invalidate_blocks()
(no matching commit)
- [f2fs-dev,v4,4/4] f2fs: Optimize f2fs_truncate_data_blocks_range()
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists