From: Andy Walls <awalls@radix.net>
To: Chris Friesen <cfriesen@nortel.com>
Cc: 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 19:38:34 -0500 [thread overview]
Message-ID: <1264552714.3089.2.camel@palomino.walls.org> (raw)
In-Reply-To: <4B5F54DE.7030302@nortel.com>
On Tue, 2010-01-26 at 14:47 -0600, Chris Friesen wrote:
> 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
VmallocUsed referws to Vmalloc address space consumption. However,
Vmalloc address space is not used exclusively to map system RAM into
virtual address space. It is also used to map PCI MMIO windows to the
register sets or memory chips on PCI cards into the vritual address
space.
Regards,
Andy
> (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 from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
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>
next prev parent reply other threads:[~2010-01-27 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 19:03 Chris Friesen
2010-01-26 20:47 ` Chris Friesen
2010-01-26 23:48 ` Chris Friesen
2010-01-27 0:38 ` Andy Walls [this message]
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=1264552714.3089.2.camel@palomino.walls.org \
--to=awalls@radix.net \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox