mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yi Sun <yi.sun@unisoc.com>
To: <chao@kernel.org>, <jaegeuk@kernel.org>
Cc: <sunyibuaa@gmail.com>, <yi.sun@unisoc.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: [PATCH v4 0/4] Speed up f2fs truncate
Date: Mon, 23 Dec 2024 16:10:40 +0800	[thread overview]
Message-ID: <20241223081044.1126291-1-yi.sun@unisoc.com> (raw)

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.

Test steps:
Set the CPU and DDR frequencies to the maximum.
dd if=/dev/random of=./test.txt bs=1M count=100000
sync
rm test.txt

Time Comparison of rm:
original        optimization            ratio
7.17s           3.27s                   54.39%

----
v4:
- introduce update_sit_entry_for_alloc().
- [patch 2,3,4 / 4] have no changes compared to v3.

Yi Sun (4):
  f2fs: introduce update_sit_entry_for_release/alloc()
  f2fs: update_sit_entry_for_release() supports consecutive blocks.
  f2fs: add parameter @len to f2fs_invalidate_blocks()
  f2fs: Optimize f2fs_truncate_data_blocks_range()

 fs/f2fs/compress.c |   4 +-
 fs/f2fs/f2fs.h     |   3 +-
 fs/f2fs/file.c     |  78 +++++++++++++++++--
 fs/f2fs/node.c     |   4 +-
 fs/f2fs/segment.c  | 185 +++++++++++++++++++++++++++++----------------
 5 files changed, 198 insertions(+), 76 deletions(-)

-- 
2.25.1


             reply	other threads:[~2024-12-23  8:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-23  8:10 Yi Sun [this message]
2024-12-23  8:10 ` [PATCH v4 1/4] f2fs: introduce update_sit_entry_for_release/alloc() Yi Sun
2024-12-26 14:00   ` Chao Yu
2024-12-23  8:10 ` [PATCH v4 2/4] f2fs: update_sit_entry_for_release() supports consecutive blocks Yi Sun
2024-12-26 14:16   ` Chao Yu
2024-12-23  8:10 ` [PATCH v4 3/4] f2fs: add parameter @len to f2fs_invalidate_blocks() Yi Sun
2025-01-13 13:49   ` Chao Yu
2024-12-23  8:10 ` [PATCH v4 4/4] f2fs: Optimize f2fs_truncate_data_blocks_range() Yi Sun
2025-01-14  4:28   ` Chao Yu
2025-01-15  5:09     ` 答复: " 孙毅 (Yi Sun)
2025-01-08 18:40 ` [f2fs-dev] [PATCH v4 0/4] Speed up f2fs truncate patchwork-bot+f2fs
2025-01-13 18:51 ` 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=20241223081044.1126291-1-yi.sun@unisoc.com \
    --to=yi.sun@unisoc.com \
    --cc=Hao_hao.Wang@unisoc.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=ke.wang@unisoc.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niuzhiguo84@gmail.com \
    --cc=sunyibuaa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®