How to interpret cat /proc/meminfo
Hi all, Here in my device cat /proc/meminfo is showing the following result, MemTotal: 767960 kB MemFree: 104252 kB Buffers: 14696 kB Cached: 183676 kB SwapCached: 0 kB Active: 304596 kB Inactive: 282020 kB Active(anon): 250560 kB Inactive(anon): 139488 kB Active(file): 54036 kB Inactive(file): 142532 kB Unevictable: 988 kB Mlocked: 0 kB HighTotal: 536576 kB HighFree: 23408 kB LowTotal: 231384 kB LowFree: 80844 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 389252 kB Mapped: 94368 kB Shmem: 816 kB Slab: 17932 kB SReclaimable: 7388 kB SUnreclaim: 10544 kB KernelStack: 5912 kB PageTables: 20064 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 383980 kB Committed_AS: 3685728 kB VmallocTotal: 434176 kB VmallocUsed: 261584 kB VmallocChunk: 115324 kB && My kernel virtual memory lay out is like this, <5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) <5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) <5>[ 0.000000] DMA : 0xff000000 - 0xffe00000 ( 14 MB) <5>[ 0.000000] vmalloc : 0xdf800000 - 0xfa000000 ( 424 MB) <5>[ 0.000000] lowmem : 0xc0000000 - 0xdf000000 ( 496 MB) <5>[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) <5>[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) <5>[ 0.000000] .init : 0xc0008000 - 0xc0049000 ( 260 kB) <5>[ 0.000000] .text : 0xc0100000 - 0xc0a26000 (9368 kB) <5>[ 0.000000] .data : 0xc0b00000 - 0xc0c464c0 (1306 kB) && In the kernel command line i had put the "vmalloc=432MB" , to reserve the vmalloc area. My question is, While in the kernel memory layout, lowmem is shown as 496MB, in /proc/meminfo LowMEMtotal is only 231MB. Why is the difference between the two? How to increase the Lowmem size with reserving my vmalloc region memory(432MB) -- With regards, Sandeep Kumar Anantapalli,
Hi... On Fri, Oct 21, 2011 at 14:29, sandeep kumar <coolsandyforyou@gmail.com> wrote:
My question is, While in the kernel memory layout, lowmem is shown as 496MB, in /proc/meminfo LowMEMtotal is only 231MB. Why is the difference between the two?
Maybe there's a device memory mapped in the lowmem region. Check using tools like "lspci" or such. I can't think of another possibility right now, so others might add... BTW, it's a bit surprised me. Looking at the amount of your total RAM, it should be all mapped in low mem. I wonder, why some of them are shifted into high mem... ANd the amount of committed_AS...that is really big compared to your actual RAM, don't you agree? -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
participants (2)
-
Mulyadi Santosa -
sandeep kumar