From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [PATCH 4/5] f2fs: prevent an f2fs_gc loop during disable_checkpoint
Date: Fri, 23 Feb 2024 12:55:34 -0800 [thread overview]
Message-ID: <20240223205535.307307-4-jaegeuk@kernel.org> (raw)
In-Reply-To: <20240223205535.307307-1-jaegeuk@kernel.org>
Don't get stuck in the f2fs_gc loop while disabling checkpoint. Instead, we have
a time-based management.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/super.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index fc7f1a9fbbda..7d9b92978709 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -2191,6 +2191,7 @@ static int f2fs_disable_checkpoint(struct f2fs_sb_info *sbi)
.init_gc_type = FG_GC,
.should_migrate_blocks = false,
.err_gc_skipped = true,
+ .no_bg_gc = true,
.nr_free_secs = 1 };
f2fs_down_write(&sbi->gc_lock);
--
2.44.0.rc0.258.g7320e95886-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH 4/5] f2fs: prevent an f2fs_gc loop during disable_checkpoint
Date: Fri, 23 Feb 2024 12:55:34 -0800 [thread overview]
Message-ID: <20240223205535.307307-4-jaegeuk@kernel.org> (raw)
In-Reply-To: <20240223205535.307307-1-jaegeuk@kernel.org>
Don't get stuck in the f2fs_gc loop while disabling checkpoint. Instead, we have
a time-based management.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/super.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index fc7f1a9fbbda..7d9b92978709 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -2191,6 +2191,7 @@ static int f2fs_disable_checkpoint(struct f2fs_sb_info *sbi)
.init_gc_type = FG_GC,
.should_migrate_blocks = false,
.err_gc_skipped = true,
+ .no_bg_gc = true,
.nr_free_secs = 1 };
f2fs_down_write(&sbi->gc_lock);
--
2.44.0.rc0.258.g7320e95886-goog
next prev parent reply other threads:[~2024-02-23 20:55 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 20:55 [f2fs-dev] [PATCH 1/5] f2fs: check number of blocks in a current section Jaegeuk Kim
2024-02-23 20:55 ` Jaegeuk Kim
2024-02-23 20:55 ` [f2fs-dev] [PATCH 2/5] f2fs: fix write pointers all the time Jaegeuk Kim
2024-02-23 20:55 ` Jaegeuk Kim
2024-02-26 2:48 ` [f2fs-dev] " Chao Yu
2024-02-26 2:48 ` Chao Yu
2024-02-26 17:33 ` Daeho Jeong
2024-02-26 17:33 ` Daeho Jeong
2024-02-27 1:00 ` Jaegeuk Kim
2024-02-27 1:00 ` Jaegeuk Kim
2024-02-27 0:59 ` [f2fs-dev] [PATCH 2/5 v2] " Jaegeuk Kim
2024-02-27 0:59 ` Jaegeuk Kim
2024-02-27 6:19 ` [f2fs-dev] " Chao Yu
2024-02-27 6:19 ` Chao Yu
2024-02-23 20:55 ` [f2fs-dev] [PATCH 3/5] f2fs: print zone status in string and some log Jaegeuk Kim
2024-02-23 20:55 ` Jaegeuk Kim
2024-02-26 2:54 ` [f2fs-dev] " Chao Yu
2024-02-26 2:54 ` Chao Yu
2024-02-26 19:03 ` Daeho Jeong
2024-02-26 19:03 ` Daeho Jeong
2024-02-26 22:52 ` [f2fs-dev] [PATCH 3/5 v2] " Jaegeuk Kim
2024-02-26 22:52 ` Jaegeuk Kim
2024-02-27 6:26 ` [f2fs-dev] " Chao Yu
2024-02-27 6:26 ` Chao Yu
2024-03-04 17:47 ` [f2fs-dev] [PATCH 3/5] " Jaegeuk Kim
2024-03-04 17:47 ` Jaegeuk Kim
2024-02-23 20:55 ` Jaegeuk Kim [this message]
2024-02-23 20:55 ` [PATCH 4/5] f2fs: prevent an f2fs_gc loop during disable_checkpoint Jaegeuk Kim
2024-02-26 2:58 ` [f2fs-dev] " Chao Yu
2024-02-26 2:58 ` Chao Yu
2024-02-26 19:14 ` Daeho Jeong
2024-02-26 19:14 ` Daeho Jeong
2024-02-23 20:55 ` [f2fs-dev] [PATCH 5/5] f2fs: allow to mount if cap is 100 Jaegeuk Kim
2024-02-23 20:55 ` Jaegeuk Kim
2024-02-26 2:59 ` [f2fs-dev] " Chao Yu
2024-02-26 2:59 ` Chao Yu
2024-02-26 19:34 ` Daeho Jeong
2024-02-26 19:34 ` Daeho Jeong
2024-02-26 22:47 ` Jaegeuk Kim
2024-02-26 22:47 ` Jaegeuk Kim
2024-02-28 3:47 ` Daeho Jeong
2024-02-28 3:47 ` Daeho Jeong
2024-02-26 2:40 ` [f2fs-dev] [PATCH 1/5] f2fs: check number of blocks in a current section Chao Yu
2024-02-26 2:40 ` Chao Yu
2024-02-26 17:17 ` Daeho Jeong
2024-02-26 17:17 ` Daeho Jeong
2024-02-26 23:14 ` [f2fs-dev] [PATCH 1/5 v2] " Jaegeuk Kim
2024-02-26 23:14 ` Jaegeuk Kim
2024-02-27 6:08 ` [f2fs-dev] " Chao Yu
2024-02-27 6:08 ` Chao Yu
2024-02-28 22:50 ` [f2fs-dev] [PATCH 1/5] " patchwork-bot+f2fs
2024-02-28 22:50 ` 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=20240223205535.307307-4-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.