From: Chao Yu <chao@kernel.org>
To: Yangtao Li <frank.li@vivo.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: make gc_idle sysfs node readable
Date: Tue, 25 Oct 2022 10:51:33 +0800 [thread overview]
Message-ID: <429625d3-ca81-d067-deb7-e9d40725eaf0@kernel.org> (raw)
In-Reply-To: <20221025023334.77096-1-frank.li@vivo.com>
On 2022/10/25 10:33, Yangtao Li wrote:
> Hi Chao,
>
> What: /sys/fs/f2fs/<disk>/gc_idle
> Date: July 2013
> Contact: "Namjae Jeon" <namjae.jeon@samsung.com>
> Description: Controls the victim selection policy for garbage collection.
> Setting gc_idle = 0(default) will disable this option. Setting:
>
> =========== ===============================================
> gc_idle = 1 will select the Cost Benefit approach & setting
> gc_idle = 2 will select the greedy approach & setting
> gc_idle = 3 will select the age-threshold based approach.
> =========== ===============================================
>
> From the kernel documentation, this node only describes the writing of
> the value, and does not describe the reading of the value.
If the value is used by userspace program, after the change, it will break
userspace.
>
> Actually, this modification does the same thing as commit e60aeb2dee1a
> ("f2fs: make gc_urgent and gc_segment_mode sysfs node readabl").
> I understand it is an addition to the omission of the patch above.
>
> Why gc_urgent and gc_segment_mode can be modified to string, but gc_idle
> breaks forward compatibility?
Oops, I guess that patch may have caused a regression...if there is any
user..
>
> Thanks,
prev parent reply other threads:[~2022-10-25 2:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 8:26 Yangtao Li
2022-10-25 1:53 ` Chao Yu
2022-10-25 2:33 ` [f2fs-dev] " Yangtao Li
2022-10-25 2:51 ` Chao Yu [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=429625d3-ca81-d067-deb7-e9d40725eaf0@kernel.org \
--to=chao@kernel.org \
--cc=frank.li@vivo.com \
--cc=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 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®