mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* VmallocTotal meminfo
@ 2005-06-11 20:27 Jan Engelhardt
  2005-06-11 23:39 ` Alexander Nyberg
  0 siblings, 1 reply; 2+ messages in thread
From: Jan Engelhardt @ 2005-06-11 20:27 UTC (permalink / raw)
  To: Linux Kernel Mailing List

Hi,


/proc/meminfo:
MemTotal:       256656 kB
MemFree:         32480 kB
...
LowTotal:       256656 kB
LowFree:         32480 kB
SwapTotal:      530136 kB
SwapFree:       530136 kB
...
VmallocTotal:   778164 kB
VmallocUsed:     22468 kB
VmallocChunk:   755404 kB

What's the VmallocTotal telling me? How is it calculated?
I ask because running a surprisingly modern Linux on a surprisingly ancient 
machine results in VmallocTotal being somewhere in the 1-gigabyte range, which 
can _never_ ever be.



Jan Engelhardt                                                               
--                                                                            
| Gesellschaft fuer Wissenschaftliche Datenverarbeitung Goettingen,
| Am Fassberg, 37077 Goettingen, www.gwdg.de

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: VmallocTotal meminfo
  2005-06-11 20:27 VmallocTotal meminfo Jan Engelhardt
@ 2005-06-11 23:39 ` Alexander Nyberg
  0 siblings, 0 replies; 2+ messages in thread
From: Alexander Nyberg @ 2005-06-11 23:39 UTC (permalink / raw)
  To: Jan Engelhardt; +Cc: Linux Kernel Mailing List

lör 2005-06-11 klockan 22:27 +0200 skrev Jan Engelhardt:
> Hi,
> 
> 
> /proc/meminfo:
> MemTotal:       256656 kB
> MemFree:         32480 kB
> ...
> LowTotal:       256656 kB
> LowFree:         32480 kB
> SwapTotal:      530136 kB
> SwapFree:       530136 kB
> ...
> VmallocTotal:   778164 kB
> VmallocUsed:     22468 kB
> VmallocChunk:   755404 kB
> 
> What's the VmallocTotal telling me? How is it calculated?
> I ask because running a surprisingly modern Linux on a surprisingly ancient 
> machine results in VmallocTotal being somewhere in the 1-gigabyte range, which 
> can _never_ ever be.

The kernel has one gigabyte to map on x86. In your case 256M is used for
RAM and the most of the rest can go to vmalloc. VmallocTotal merely
indicates the amount of virtual memory that can be used for vmalloc'ed
(non-contigous) mappings. There's not much more fun to do with the
remaining kernel virtual memory so...

There's really not much to it.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-06-11 23:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-11 20:27 VmallocTotal meminfo Jan Engelhardt
2005-06-11 23:39 ` Alexander Nyberg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®