public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
	daehojeong@google.com
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: fix to freeze GC and discard threads quickly
Date: Tue, 24 Mar 2026 17:32:24 +0000	[thread overview]
Message-ID: <177437354479.1223048.17658150740894474730.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260316185954.2185806-1-daeho43@gmail.com>

Hello:

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

On Mon, 16 Mar 2026 11:59:54 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
> 
> Suspend can fail if kernel threads do not freeze for a while.
> f2fs_gc and f2fs_discard threads can perform long-running operations
> that prevent them from reaching a freeze point in a timely manner.
> 
> This patch adds explicit freezing checks in the following locations:
> 1. f2fs_gc: Added a check at the 'retry' label to exit the loop quickly
>    if freezing is requested, especially during heavy GC rounds.
> 2. __issue_discard_cmd: Added a 'suspended' flag to break both inner and
>    outer loops during discard command issuance if freezing is detected
>    after at least one command has been issued.
> 3. __issue_discard_cmd_orderly: Added a similar check for orderly discard
>    to ensure responsiveness.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v3] f2fs: fix to freeze GC and discard threads quickly
    https://git.kernel.org/jaegeuk/f2fs/c/62b45b0ad4cd

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



      parent reply	other threads:[~2026-03-24 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 18:59 [PATCH v3] f2fs: fix to freeze GC and discard threads quickly Daeho Jeong
2026-03-17  1:56 ` [f2fs-dev] " Chao Yu
2026-03-17 16:15   ` Daeho Jeong
2026-03-18  4:02     ` Chao Yu
2026-03-18  4:03 ` Chao Yu
2026-03-24 17:32 ` 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=177437354479.1223048.17658150740894474730.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=daeho43@gmail.com \
    --cc=daehojeong@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.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