on 02/12/2011 19:13 Steven Hartland said the following:
[snip]
> Given this starting point the following links provided me with addtional
> information:-
> http://www.freebsd.org/doc/en/books/arch-handbook/vm.html
> http://www.freebsd.org/doc/en/books/design-44bsd/overview-memory-management.html
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vm-design/
> http://www.cse.chalmers.se/edu/course/EDA203/unix4.pdf
> 
> I was under the incorrect impression that Virtual Memory (VM) was so named as 
> it
> was a unified physical memory and swap (virtual memory), but its not that 
> simple,
> as other items such as file-backed objects also count to this total which 
> would
> never show in physical or swap allocation of other tools such as top and 
> swapinfo.
> 
> So what I believe is now the big cause of virtual memory uplift vs the memory
> totals shown by ps / top is that the vm totals include things like file backed
> memory mapped process binaries, shared libs etc many multiple times.
> 
> This would explain why this specific machine shows the applification more than
> others here as it runs thousands of very small lightweight processes.
> 
> Thanks for pointer Andy, I now understand a lot more about the BSD VMS :)
> 
> What do people think about expanding that entry in the man page of vmstat to
> clarify just what active "virtual pages" really means?

Thank you for the excellent additional research.
I think that the expanded explanation would be very appreciated, but only if it
is completely correct and unambiguous from technical perspective.  That might
not be trivial to achieve, but is realistic :-)

P.S. I think that it would also be nice to further breakdown VM stats by type of
object e.g. anonymous (swap-backed) memory vs file-backed backed memory, etc.

Proportional RSS reporting is another nice to have feature.

-- 
Andriy Gapon
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Reply via email to