From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 205203] New: ram_thresh default (DEF_RAM_THRESHOLD) is wrong (outdated) in f2fs document
Date: Tue, 15 Oct 2019 18:25:36 +0000 [thread overview]
Message-ID: <bug-205203-202145@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205203
Bug ID: 205203
Summary: ram_thresh default (DEF_RAM_THRESHOLD) is wrong
(outdated) in f2fs document
Product: File System
Version: 2.5
Kernel Version: all
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: f2fs
Assignee: filesystem_f2fs@kernel-bugs.kernel.org
Reporter: yfdyh000@gmail.com
Regression: No
The default value appears to have been corrected by "f2fs: fix wrong
percentage" commit[1], but still the old values in the f2fs document[2].
ref:
1:
https://github.com/torvalds/linux/commit/29710bcf9426c84bb6a9b1d94316895ed6143813
2: https://www.kernel.org/doc/Documentation/filesystems/f2fs.txt
introduces ram_thresh: https://lore.kernel.org/patchwork/patch/450476/
define DEF_RAM_THRESHOLD 1:
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git/tree/fs/f2fs/node.h?h=linux-4.19.y#n23
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2019-10-15 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 18:25 bugzilla-daemon [this message]
2019-10-22 9:29 ` [f2fs-dev] [Bug 205203] ram_thresh default (DEF_RAM_THRESHOLD) is wrong (outdated) in f2fs document bugzilla-daemon
2019-12-26 1:37 ` bugzilla-daemon
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=bug-205203-202145@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).