lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 28 Sep 2009 11:32:22 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Frans Pop <elendil@...net.nl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Wrong Vmalloc numbers in /proc/meminfo

On Mon, 28 Sep 2009 02:09:30 +0200
Frans Pop <elendil@...net.nl> wrote:

> With 2.6.31 (on x86_64) I'm seeing the following in /proc/meminfo.
> 
> $ cat /proc/meminfo
> MemTotal:        2030968 kB
> MemFree:          539408 kB
> Buffers:           94984 kB
> Cached:           308564 kB
> SwapCached:        16048 kB
> Active:           652236 kB
> Inactive:         428808 kB
> Active(anon):     436808 kB
> Inactive(anon):   246996 kB
> Active(file):     215428 kB
> Inactive(file):   181812 kB
> Unevictable:        1632 kB
> Mlocked:            1632 kB
> SwapTotal:       2097144 kB
> SwapFree:        1979524 kB
> Dirty:                12 kB
> Writeback:             0 kB
> AnonPages:        671276 kB
> Mapped:            57684 kB
> Slab:             177692 kB
> SReclaimable:     160516 kB
> SUnreclaim:        17176 kB
> PageTables:        14812 kB
> NFS_Unstable:          0 kB
> Bounce:                0 kB
> WritebackTmp:          0 kB
> CommitLimit:     3112628 kB
> Committed_AS:     988780 kB
> VmallocTotal:   34359738367 kB
> VmallocUsed:      340084 kB
> VmallocChunk:   34359387131 kB
> DirectMap4k:     2008768 kB
> DirectMap2M:       63488 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.

On my x86-64 box.
VmallocTotal:   34359738367 kB
VmallocUsed:      100856 kB
VmallocChunk:   34359583863 kB

Then,
34359738367 - 34359583863
154504

Then difference is 13412 (pages) 

Hmm. in /proc/vmallocinfo
==
..
0xffffc9000652b000-0xffffc9000672c000 2101248 sys_swapon+0x6a2/0xcd0 pages=512 vmalloc N0=512
0xffffc90007efd000-0xffffc90008dde000 15601664 pcpu_alloc+0x3ad/0x4e0 vmalloc
0xffffc900096d9000-0xffffc900096dd000   16384 e1000e_setup_tx_resources+0x39/0xe0 [e1000e] pages=3 vmalloc N0=3
0xffffc900096de000-0xffffc900096e2000   16384 e1000e_setup_rx_resources+0x37/0x160 [e1000e] pages=3 vmalloc N0=3
==

It seems some amount of memory holes (rather than PAGESIZE) between vmalloc area
info.(especially around pcpu_alloc..) please check /proc/vmallocinfo if you
feel something strange.


Thanks,
-Kame


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

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ