Re: Wrong Vmalloc numbers in /proc/meminfo

[KAMEZAWA Hiroyuki]

On Mon, 28 Sep 2009 18:56:08 +0200
Frans Pop <elendil@xxxxxxxxx> wrote:

> On Monday 28 September 2009, KAMEZAWA Hiroyuki wrote:
> > > VmallocTotal:   34359738367 kB
> > > VmallocUsed:      340084 kB
> > > VmallocChunk:   34359387131 kB
> > >
> > > Is it me or are VmallocTotal and VmallocChunk off by a factor 10,000
> > > or so?
> >
> > I'm sorry I misunderstand your 10,000 implies.
> 
> What I meant is: is the Vmalloc area really 32 *terra*bytes in size?
> Seems rather big for a system with only 2GB RAM.
> 
VmallocTotal means "available address space size for VMALLOC"
It's fixed size as VMALLOC_END - VMALLOC_START.
VmallocChunk just means "free space in VMALLOC area".
Both of them are not related to size of RAM.

> I'd never noticed it before and it looks strange to me, but I guess it's 
> just the result of having 64-bit addressing: a theoretically addressable 
> area most of which will never actually be used?
> 
you're right. Most of space will never used.

Regards,
-Kame

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/