From: Yangtao Li <frank.li@vivo.com>
To: jaegeuk@kernel.org, chao@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: add missing doc for fault injection sysfs
Date: Thu, 15 Dec 2022 22:14:12 +0800 [thread overview]
Message-ID: <20221215141412.66752-1-frank.li@vivo.com> (raw)
In-Reply-To: <20221215134844.12951-1-chao@kernel.org>
Hi Chao,
> -What: /sys/fs/f2fs/<disk>/gc_mode
> -Date: October 2022
> -Contact: "Yangtao Li" <frank.li@vivo.com>
> -Description: Show the current gc_mode as a string.
> - This is a read-only entry.
> -What: /sys/fs/f2fs/<disk>/discard_urgent_util
> -Date: November 2022
> -Contact: "Yangtao Li" <frank.li@vivo.com>
> -Description: When space utilization exceeds this, do background DISCARD aggressively.
> - Does DISCARD forcibly in a period of given min_discard_issue_time when the number
> - of discards is not 0 and set discard granularity to 1.
> - Default: 80
> -
> -What: /sys/fs/f2fs/<disk>/hot_data_age_threshold
> -Date: November 2022
> -Contact: "Ping Xiong" <xiongping1@xiaomi.com>
> -Description: When DATA SEPARATION is on, it controls the age threshold to indicate
> - the data blocks as hot. By default it was initialized as 262144 blocks
> - (equals to 1GB).
> -
> -What: /sys/fs/f2fs/<disk>/warm_data_age_threshold
> -Date: November 2022
> -Contact: "Ping Xiong" <xiongping1@xiaomi.com>
> -Description: When DATA SEPARATION is on, it controls the age threshold to indicate
> - the data blocks as warm. By default it was initialized as 2621440 blocks
> - (equals to 10GB).
Why delete other node descriptions, mistake?
Thx,
Yangtao
next prev parent reply other threads:[~2022-12-15 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 13:48 Chao Yu
2022-12-15 14:14 ` Yangtao Li [this message]
2022-12-15 14:38 ` Chao Yu
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=20221215141412.66752-1-frank.li@vivo.com \
--to=frank.li@vivo.com \
--cc=chao@kernel.org \
--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®