From: Christian Kujau <lists@nerdbynature.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.25-rc3: 34TB vmalloc total -- overflow in /proc/meminfo?
Date: Wed, 5 Mar 2008 20:49:22 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.1.00.0803052038410.8658@sheep.housecafe.de> (raw)
In-Reply-To: <20080305090610.GA30024@atrey.karlin.mff.cuni.cz>
On Wed, 5 Mar 2008, Pavel Machek wrote:
> CommitLimit: 4132360 kB
> Committed_AS: 27684 kB
> VmallocTotal: 34359738367 kB
> VmallocUsed: 18112 kB
> VmallocChunk: 34359720115 kB
out of curiosity: yesterday I've seen a box[0] with ~4 TB Committed_AS:
CommitLimit: 3085152 kB
Committed_AS: 4281048084 kB
VmallocTotal: 118776 kB
VmallocUsed: 13772 kB
VmallocChunk: 103880 kB
Since it's a rather old kernel (2.6.19.2), I just want to know: could this
be related to what you've seen or this completely different (and
Committed_AS is just this high because some st00pid app has allocated this
much memory but not freed again)?
Thanks,
Christian.
[0] amd64, 32bit kernel, 32bit userland, 4GB RAM
--
BOFH excuse #101:
Collapsed Backbone
next prev parent reply other threads:[~2008-03-05 19:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 9:06 Pavel Machek
2008-03-05 9:36 ` Pavel Machek
2008-03-05 9:39 ` Pavel Machek
2008-03-05 22:12 ` Rafael J. Wysocki
2008-03-05 22:31 ` Andi Kleen
2008-03-06 11:14 ` Ingo Molnar
2008-03-06 11:30 ` Andi Kleen
2008-03-06 21:06 ` Ingo Molnar
2008-03-06 10:43 ` Pavel Machek
2008-03-05 19:49 ` Christian Kujau [this message]
2008-03-05 21:11 ` Hugh Dickins
2008-03-05 21:21 ` Pavel Machek
2008-03-05 21:36 ` Hugh Dickins
2008-03-05 22:11 ` Christian Kujau
2008-03-05 23:21 ` Hugh Dickins
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=alpine.DEB.1.00.0803052038410.8658@sheep.housecafe.de \
--to=lists@nerdbynature.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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®