* FW: process virtual size versus resident size versus swap space versus oom-killer
@ 2009-05-19 17:35 Nick Hennenfent (nhennefe)
0 siblings, 0 replies; only message in thread
From: Nick Hennenfent (nhennefe) @ 2009-05-19 17:35 UTC (permalink / raw)
To: linux-mm
I have an embedded system where the resident size of a process continues
to grow and grow
until a lot of pages have been swapped, then the oom-killer kicks in and
kills it.
How can I tell what processes or parts of processes are being swapped
out????
How can I tell what has triggered the oom-killer - is it an application
allocation or a kernel allocation???
How can I tell what part of a program is causing the resident set size
to grow????
The virtual size of the process is much larger than the resident size,
as I understand it, the resident size grows as pages become "active".
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-05-19 17:31 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-05-19 17:35 FW: process virtual size versus resident size versus swap space versus oom-killer Nick Hennenfent (nhennefe)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox