All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: which fields in /proc/meminfo are orthogonal?
Date: Tue, 26 Jan 2010 14:47:26 -0600	[thread overview]
Message-ID: <4B5F54DE.7030302@nortel.com> (raw)
In-Reply-To: <4B5F3C9C.3050908@nortel.com>

On 01/26/2010 01:03 PM, Chris Friesen wrote:

> I'm currently trying to figure out which of the entries in /proc/meminfo
> are actually orthogonal to each other.  Ideally I'd like to be able to
> add up the suitable entries and have it work out to the total memory on
> the system, so that I can then narrow down exactly where the memory is
> going.  Is this feasable?

I've tried adding up
MemFree+Buffers+Cached+AnonPages+Mapped+Slab+PageTables+VmallocUsed

(hugepages are disabled and there is no swap)

Shortly after boot this gets me within about 3MB of MemTotal.  However,
after 1070 minutes there is a 64MB difference between MemTotal and the
above sum.

Here's /proc/meminfo after 1070 minutes:

MemTotal:      4042848 kB
MemFree:        406112 kB
Buffers:         12072 kB
Cached:        3068368 kB
SwapCached:          0 kB
Active:         671200 kB
Inactive:      2711952 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:              44 kB
Writeback:           0 kB
AnonPages:      235864 kB
Mapped:          30752 kB
Slab:           200156 kB
SReclaimable:   142828 kB
SUnreclaim:      57328 kB
PageTables:       4320 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
WritebackTmp:        0 kB
CommitLimit:   2021424 kB
Committed_AS:  2593116 kB
VmallocTotal: 34359738367 kB
VmallocUsed:     21496 kB
VmallocChunk: 34359716779 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
HugePages_Surp:      0
Hugepagesize:     2048 kB
DirectMap4k:      3008 kB
DirectMap2M:   4190208 kB

Any ideas how to track down the missing memory?

Chris

WARNING: multiple messages have this Message-ID (diff)
From: "Chris Friesen" <cfriesen@nortel.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: which fields in /proc/meminfo are orthogonal?
Date: Tue, 26 Jan 2010 14:47:26 -0600	[thread overview]
Message-ID: <4B5F54DE.7030302@nortel.com> (raw)
In-Reply-To: <4B5F3C9C.3050908@nortel.com>

On 01/26/2010 01:03 PM, Chris Friesen wrote:

> I'm currently trying to figure out which of the entries in /proc/meminfo
> are actually orthogonal to each other.  Ideally I'd like to be able to
> add up the suitable entries and have it work out to the total memory on
> the system, so that I can then narrow down exactly where the memory is
> going.  Is this feasable?

I've tried adding up
MemFree+Buffers+Cached+AnonPages+Mapped+Slab+PageTables+VmallocUsed

(hugepages are disabled and there is no swap)

Shortly after boot this gets me within about 3MB of MemTotal.  However,
after 1070 minutes there is a 64MB difference between MemTotal and the
above sum.

Here's /proc/meminfo after 1070 minutes:

MemTotal:      4042848 kB
MemFree:        406112 kB
Buffers:         12072 kB
Cached:        3068368 kB
SwapCached:          0 kB
Active:         671200 kB
Inactive:      2711952 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:              44 kB
Writeback:           0 kB
AnonPages:      235864 kB
Mapped:          30752 kB
Slab:           200156 kB
SReclaimable:   142828 kB
SUnreclaim:      57328 kB
PageTables:       4320 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
WritebackTmp:        0 kB
CommitLimit:   2021424 kB
Committed_AS:  2593116 kB
VmallocTotal: 34359738367 kB
VmallocUsed:     21496 kB
VmallocChunk: 34359716779 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
HugePages_Surp:      0
Hugepagesize:     2048 kB
DirectMap4k:      3008 kB
DirectMap2M:   4190208 kB

Any ideas how to track down the missing memory?

Chris

--
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:[~2010-01-26 20:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 19:03 which fields in /proc/meminfo are orthogonal? Chris Friesen
2010-01-26 19:03 ` Chris Friesen
2010-01-26 20:47 ` Chris Friesen [this message]
2010-01-26 20:47   ` Chris Friesen
2010-01-26 23:48   ` Chris Friesen
2010-01-26 23:48     ` Chris Friesen
2010-01-27  0:38   ` Andy Walls
2010-01-27  0:38     ` Andy Walls
2010-08-03 17:06     ` meherjaya
2010-01-27  0:55   ` Jeff Dike
2010-01-27  0:55     ` Jeff Dike

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=4B5F54DE.7030302@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.