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

Hi!

> > > CommitLimit:   4132360 kB
> > > Committed_AS:    27684 kB
> > > VmallocTotal: 34359738367 kB
> > > VmallocUsed:     18112 kB
> > > VmallocChunk: 34359720115 kB
> 
> 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.

Hmm... ok, I see, I thought "clearly this overflowed somewhere", and I
was wrong, it is expected result.

Still.... what is 34TB of vmalloc space good for when we can only ever
allocate 4GB (because that is how much physical memory we have?)? To
prevent fragmentation? 

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-03-05 21:21 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 [this message]
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=20080305212139.GA31999@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --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).