linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: linux-mm@kvack.org
Cc: pbadari@us.ibm.com, Dave Hansen <haveblue@us.ibm.com>
Subject: [PATCH] update /proc/meminfo Buffers documentation
Date: Thu, 13 Jul 2006 10:15:17 -0700	[thread overview]
Message-ID: <20060713171517.8B324CD3@localhost.localdomain> (raw)

The filesystems/proc.txt meminfo documentation is a wee bit inaccurate
with respect to buffers.  They can get a bit bigger than 20MB, and I have
proof ;).  I copied a description that Badari gave me on IRC for this
patch.

$ cat /proc/meminfo
MemTotal:     16375148 kB
MemFree:       9372524 kB
Buffers:        818276 kB
Cached:        4923044 kB
SwapCached:          0 kB
Active:        3517596 kB
Inactive:      2437724 kB
HighTotal:    14548952 kB
HighFree:      9355304 kB
LowTotal:      1826196 kB
LowFree:         17220 kB
SwapTotal:    32611940 kB
SwapFree:     32610724 kB
Dirty:            5932 kB
Writeback:           0 kB
Mapped:         231172 kB
Slab:           977396 kB
CommitLimit:  40799512 kB
Committed_AS:  1373664 kB
PageTables:       7412 kB
VmallocTotal:   116728 kB
VmallocUsed:     16408 kB
VmallocChunk:   100104 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


---

 lxc-dave/Documentation/filesystems/proc.txt |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff -puN Documentation/filesystems/proc.txt~update-meminfo-documentation Documentation/filesystems/proc.txt
--- lxc/Documentation/filesystems/proc.txt~update-meminfo-documentation	2006-07-13 10:07:18.000000000 -0700
+++ lxc-dave/Documentation/filesystems/proc.txt	2006-07-13 10:07:19.000000000 -0700
@@ -389,8 +389,9 @@ VmallocChunk:   111088 kB
     MemTotal: Total usable ram (i.e. physical ram minus a few reserved
               bits and the kernel binary code)
      MemFree: The sum of LowFree+HighFree
-     Buffers: Relatively temporary storage for raw disk blocks
-              shouldn't get tremendously large (20MB or so)
+     Buffers: Relatively temporary storage for raw disk blocks.  Also
+	      used for caching filesystem metadata (like directories,
+	      indirect blocks, inode maps, block maps etc..).
       Cached: in-memory cache for files read from the disk (the
               pagecache).  Doesn't include SwapCached
   SwapCached: Memory that once was swapped out, is swapped back in but
_

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

                 reply	other threads:[~2006-07-13 17:15 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=20060713171517.8B324CD3@localhost.localdomain \
    --to=haveblue@us.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=pbadari@us.ibm.com \
    /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