mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v4 2/4] f2fs: update_sit_entry_for_release() supports consecutive blocks.
Date: Thu, 26 Dec 2024 22:16:02 +0800	[thread overview]
Message-ID: <25792358-84c1-4411-a290-0a978ebe78a2@kernel.org> (raw)
In-Reply-To: <20241223081044.1126291-3-yi.sun@unisoc.com>

On 2024/12/23 16:10, Yi Sun wrote:
> This function can process some consecutive blocks at a time.
> 
> When using update_sit_entry() to release consecutive blocks,
> ensure that the consecutive blocks belong to the same segment.
> Because after update_sit_entry_for_realese(), @segno is still
> in use in update_sit_entry().
> 
> Signed-off-by: Yi Sun <yi.sun@unisoc.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

  reply	other threads:[~2024-12-26 14:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-23  8:10 [PATCH v4 0/4] Speed up f2fs truncate Yi Sun
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 [this message]
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=25792358-84c1-4411-a290-0a978ebe78a2@kernel.org \
    --to=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=niuzhiguo84@gmail.com \
    --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
all inboxes | Powered by JetHome®