From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: sysfs: introduce critical_task_priority
Date: Tue, 10 Feb 2026 21:28:26 +0000 [thread overview]
Message-ID: <177075890633.3671709.6089678750946061436.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260204030501.85441-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 4 Feb 2026 11:05:01 +0800 you wrote:
> This patch introduces /sys/fs/f2fs/<disk>/critical_task_priority, w/
> this new sysfs interface, we can tune priority of f2fs_ckpt thread and
> f2fs_gc thread.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> Documentation/ABI/testing/sysfs-fs-f2fs | 8 ++++++++
> fs/f2fs/checkpoint.c | 2 ++
> fs/f2fs/f2fs.h | 4 ++++
> fs/f2fs/gc.c | 2 ++
> fs/f2fs/super.c | 1 +
> fs/f2fs/sysfs.c | 17 +++++++++++++++++
> 6 files changed, 34 insertions(+)
Here is the summary with links:
- [f2fs-dev] f2fs: sysfs: introduce critical_task_priority
https://git.kernel.org/jaegeuk/f2fs/c/52190933c37a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
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: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: sysfs: introduce critical_task_priority
Date: Tue, 10 Feb 2026 21:28:26 +0000 [thread overview]
Message-ID: <177075890633.3671709.6089678750946061436.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260204030501.85441-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 4 Feb 2026 11:05:01 +0800 you wrote:
> This patch introduces /sys/fs/f2fs/<disk>/critical_task_priority, w/
> this new sysfs interface, we can tune priority of f2fs_ckpt thread and
> f2fs_gc thread.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> Documentation/ABI/testing/sysfs-fs-f2fs | 8 ++++++++
> fs/f2fs/checkpoint.c | 2 ++
> fs/f2fs/f2fs.h | 4 ++++
> fs/f2fs/gc.c | 2 ++
> fs/f2fs/super.c | 1 +
> fs/f2fs/sysfs.c | 17 +++++++++++++++++
> 6 files changed, 34 insertions(+)
Here is the summary with links:
- [f2fs-dev] f2fs: sysfs: introduce critical_task_priority
https://git.kernel.org/jaegeuk/f2fs/c/52190933c37a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-02-10 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 3:05 [f2fs-dev] [PATCH] f2fs: sysfs: introduce critical_task_priority Chao Yu via Linux-f2fs-devel
2026-02-04 3:05 ` Chao Yu
2026-02-10 21:28 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-02-10 21:28 ` [f2fs-dev] " 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=177075890633.3671709.6089678750946061436.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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.