linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fang Wenqi <anton.fang@gmail.com>
To: tytso@mit.edu, adilger@sun.com
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Fang Wenqi <antonf@turbolinux.com.cn>
Subject: [PATCH] ext4: Update documentation to correct the inode_readahead_blks option name
Date: Thu, 17 Dec 2009 15:40:23 +0800	[thread overview]
Message-ID: <1261035623-28474-1-git-send-email-antonf@turbolinux.com.cn> (raw)

Per commit 240799cd, the option name for readahead should be
inode_readahead_blks, not inode_readahead.

Signed-off-by: Fang Wenqi <antonf@turbolinux.com.cn>
---
 Documentation/filesystems/ext4.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Documentation/filesystems/ext4.txt b/Documentation/filesystems/ext4.txt
index af6885c..e1def17 100644
--- a/Documentation/filesystems/ext4.txt
+++ b/Documentation/filesystems/ext4.txt
@@ -196,7 +196,7 @@ nobarrier		This also requires an IO stack which can support
 			also be used to enable or disable barriers, for
 			consistency with other ext4 mount options.
 
-inode_readahead=n	This tuning parameter controls the maximum
+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.
-- 
1.6.5.2


             reply	other threads:[~2009-12-17  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17  7:40 Fang Wenqi [this message]
2009-12-24 22:52 ` [PATCH] ext4: Update documentation to correct the inode_readahead_blks option name tytso

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=1261035623-28474-1-git-send-email-antonf@turbolinux.com.cn \
    --to=anton.fang@gmail.com \
    --cc=adilger@sun.com \
    --cc=antonf@turbolinux.com.cn \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).