mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Joris van Rantwijk" <jorispubl@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Physical memory disappeared from /proc/meminfo
Date: Tue, 24 Jun 2008 09:15:41 +0300	[thread overview]
Message-ID: <84144f020806232315q1ee89300v9a96384fb64492df@mail.gmail.com> (raw)
In-Reply-To: <2c84b89ef40f92173a026b8d95e889ad@xs4all.nl>

On Tue, Jun 24, 2008 at 8:09 AM, Joris van Rantwijk <jorispubl@xs4all.nl> wrote:
> My system got into a situation where a lot of physical memory is
> in use. I want to know where this memory is being used, but it
> seems to have become untraceable somehow.
>
> My total physical memory is 1 GB.
> Adding up all VSZ numbers from "ps auxw" gets me to about 75 MB,
> so I should have a lot of free memory but I don't see it.
>
> My kernel is Linux 2.6.25.4 for x86_64 with a 32-bit userland.
> I disabled swap to make it easier to investigate this issue.
>
> One problem is that I can't really make sense of /proc/meminfo.
> As far as I understand the numbers, I find that about 640 MB is
> unaccounted for.
>
> For example I would expect that
> MemTotal = MemFree + Buffers + Cached + AnonPages + Mapped + Slab.
>
> Is that a valid assumption?

Yes.

> Why does it not hold for my machine?
> Is this a bug in the memory statistics?
> What part of the system is using all this untraceable memory?

Likely a driver leaking full pages. Your config and dmesg would be
helpful. Last time I bumped into this, though, was with a proprietary
module...

> /proc/meminfo:
> MemTotal:     996320 kB
> MemFree:       67708 kB
> Buffers:       17716 kB
> Cached:        62412 kB
> SwapCached:        0 kB
> Active:        27320 kB
> Inactive:      58720 kB
> SwapTotal:         0 kB
> SwapFree:          0 kB
> Dirty:            12 kB
> Writeback:         0 kB
> AnonPages:      5932 kB
> Mapped:         3916 kB
> Slab:         193560 kB
> SReclaimable:  26076 kB
> SUnreclaim:   167484 kB
> PageTables:      464 kB
> NFS_Unstable:      0 kB
> Bounce:            0 kB
> CommitLimit:  498160 kB
> Comitted_AS:   15536 kB
> VmallocTotal: 34359738367 kB
> VmallocUsed:     600 kB
> VmallocChunk: 34359736326 kB
>
> Please help.
>
> Joris.
>
> --
> 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/
>

  reply	other threads:[~2008-06-24  6:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  5:09 Joris van Rantwijk
2008-06-24  6:15 ` Pekka Enberg [this message]
2008-06-24 18:25   ` Joris van Rantwijk

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=84144f020806232315q1ee89300v9a96384fb64492df@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=jorispubl@xs4all.nl \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®