From: Eryu Guan <guaneryu@gmail.com>
To: util-linux-ng@vger.kernel.org
Cc: Eryu Guan <guaneryu@gmail.com>
Subject: [PATCH] mount.8: mount option inode_readahead for ext4 should be inode_readahead_blks
Date: Wed, 11 Jul 2012 20:49:54 +0800 [thread overview]
Message-ID: <1342010994-4085-1-git-send-email-guaneryu@gmail.com> (raw)
Mount option inode_readahead should be inode_readahead_blks. Also the
value should be a power of 2.
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
---
sys-utils/mount.8 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sys-utils/mount.8 b/sys-utils/mount.8
index 0fb2448..3ddd3f1 100644
--- a/sys-utils/mount.8
+++ b/sys-utils/mount.8
@@ -1490,10 +1490,10 @@ with other ext4 mount options.
The ext4 filesystem enables write barriers by default.
.TP
-.BI inode_readahead= n
+.BI inode_readahead_blks= n
This tuning parameter controls the maximum number of inode table blocks that
ext4's inode table readahead algorithm will pre-read into the buffer cache.
-The default value is 32 blocks.
+The value must be a power of 2. The default value is 32 blocks.
.TP
.BI stripe= n
Number of filesystem blocks that mballoc will try to use for allocation size
--
1.7.10.4
next reply other threads:[~2012-07-11 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 12:49 Eryu Guan [this message]
2012-07-16 16:23 ` [PATCH] mount.8: mount option inode_readahead for ext4 should be inode_readahead_blks Karel Zak
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=1342010994-4085-1-git-send-email-guaneryu@gmail.com \
--to=guaneryu@gmail.com \
--cc=util-linux-ng@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.