mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Xiaole He <hexiaole1994@126.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix has_curseg_enough_space to check all data segments for dentry blocks
Date: Mon, 24 Nov 2025 18:50:18 +0000	[thread overview]
Message-ID: <176401021825.42009.3887972145540432748.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251111061051.337547-1-hexiaole1994@126.com>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Tue, 11 Nov 2025 14:10:51 +0800 you wrote:
> When active_logs == 6, dentry blocks can be allocated to HOT, WARM, or
> COLD segments based on various conditions in __get_segment_type_6():
> - age extent cache (if enabled)
> - FI_HOT_DATA flag (set when dirty_pages <= min_hot_blocks)
> - rw_hint (defaults to WARM via f2fs_rw_hint_to_seg_type)
> - file_is_hot(), FI_NEED_IPU, f2fs_is_cow_file(), etc.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v2] f2fs: fix has_curseg_enough_space to check all data segments for dentry blocks
    https://git.kernel.org/jaegeuk/f2fs/c/6d87364f7e94

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-11-24 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 13:26 [PATCH v1] " Xiaole He
2025-11-11  2:44 ` [f2fs-dev] " Yongpeng Yang
2025-11-11  6:00   ` [PATCH v2] " Xiaole He
2025-11-11  6:10     ` Xiaole He
2025-11-11  6:29       ` [f2fs-dev] " Yongpeng Yang
2025-11-11  7:17       ` Chao Yu
2025-11-24 18:50       ` patchwork-bot+f2fs [this message]
2025-12-02 18:00       ` Jaegeuk Kim

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=176401021825.42009.3887972145540432748.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=hexiaole1994@126.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    /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
Powered by JetHome