From: patchwork-bot+f2fs@kernel.org
To: Yi Sun <yi.sun@unisoc.com>
Cc: chao@kernel.org, ke.wang@unisoc.com,
linux-kernel@vger.kernel.org, sunyibuaa@gmail.com,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
hao_hao.wang@unisoc.com
Subject: Re: [f2fs-dev] [RFC PATCH 0/2] Speed up f2fs truncate
Date: Mon, 28 Oct 2024 17:40:40 +0000 [thread overview]
Message-ID: <173013724023.126843.9607726471702748636.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241016052758.3400359-1-yi.sun@unisoc.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 16 Oct 2024 13:27:56 +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 and belong to the same segment,
> 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,RFC,1/2] f2fs: introduce update_sit_entry_for_release()
https://git.kernel.org/jaegeuk/f2fs/c/af68d9b481ac
- [f2fs-dev,RFC,2/2] f2fs: introduce f2fs_invalidate_consecutive_blocks()
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-28 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 5:27 [RFC PATCH 0/2] Speed up f2fs truncate Yi Sun
2024-10-16 5:27 ` [RFC PATCH 1/2] f2fs: introduce update_sit_entry_for_release() Yi Sun
2024-10-16 5:27 ` [RFC PATCH 2/2] f2fs: introduce f2fs_invalidate_consecutive_blocks() Yi Sun
2024-10-16 16:04 ` Jaegeuk Kim
2024-10-17 1:40 ` Chao Yu
2024-10-24 9:54 ` yi sun
2024-10-24 10:26 ` Chao Yu
2024-10-29 3:02 ` yi sun
2024-10-28 17:40 ` patchwork-bot+f2fs [this message]
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=173013724023.126843.9607726471702748636.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=hao_hao.wang@unisoc.com \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox