LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	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 23:11:26 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0803052301340.8658@sheep.housecafe.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0803052045430.821@blonde.site>

On Wed, 5 Mar 2008, Hugh Dickins wrote:
> I don't see what Pavel's issue is with this: it's simply a fact that
> with a 64-bit kernel, we've lots of virtual address space to spare
> for vmalloc.  What would be surprising is for VmallocUsed to get up
> as high as that.

OK, thanks for the clarification.

> Completely different and much more interesting.

Well, if it's "interesting"...here are some more details from the box:

http://nerdbynature.de/bits/2.6.19.2/

> Unlikely.  Offhand I'm not quite sure that's impossible, but it's far
> more likely that we've a kernel bug and vm_committed_space has wrapped
> negative.

Huh. When I first saw this I thought "kernel bug" too, but then read the
documentation to Committed_AS I thought it's just userspace related...

> Ancient as your kernel is, I don't notice anything in the ChangeLogs
> since then to say we've fixed a bug of that kind since 2.6.19.
> Any idea how to reproduce this?

Well, the box is running fine and since it's a production machine I don't 
intend to reboot the box very often. And since it's really an old kernel 
(for lkml discussion, that is) I don't intend to debug this one further. 
I really was only curious if this was userspace related (some app 
overcommitting) or some kernel weirdness.

>  Are you using HugePages at all?

I have:

# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set

...was this, what you meant?

Thanks,
Christian.
-- 
BOFH excuse #340:

Well fix that in the next (upgrade, update, patch release, service pack).

  parent reply	other threads:[~2008-03-05 22:11 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
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 [this message]
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.0803052301340.8658@sheep.housecafe.de \
    --to=lists@nerdbynature.de \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --subject='Re: 2.6.25-rc3: 34TB vmalloc total -- overflow in /proc/meminfo?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).