From: Kinglong Mee <kinglongmee@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>, Andreas Dilger <adilger@dilger.ca>
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH] ext4: add missing description of files in /proc/fs/ext4/<devname>
Date: Mon, 02 Mar 2015 19:25:22 +0800 [thread overview]
Message-ID: <54F448A2.3090704@gmail.com> (raw)
Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
---
Documentation/filesystems/ext4.txt | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/ext4.txt b/Documentation/filesystems/ext4.txt
index 6c0108e..250c074 100644
--- a/Documentation/filesystems/ext4.txt
+++ b/Documentation/filesystems/ext4.txt
@@ -428,8 +428,10 @@ in table below.
Files in /proc/fs/ext4/<devname>
..............................................................................
- File Content
- mb_groups details of multiblock allocator buddy cache of free blocks
+ File Content
+ es_shrinker_info some statictics in extent status tree shrinker
+ mb_groups details of multiblock allocator buddy cache of free blocks
+ options mount options of filesystem
..............................................................................
/sys entries
--
2.1.0
reply other threads:[~2015-03-02 11:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54F448A2.3090704@gmail.com \
--to=kinglongmee@gmail.com \
--cc=adilger@dilger.ca \
--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).