From: "Nick Hennenfent (nhennefe)" <nhennefe@cisco.com>
To: linux-mm@kvack.org
Subject: FW: process virtual size versus resident size versus swap space versus oom-killer
Date: Tue, 19 May 2009 13:35:06 -0400 [thread overview]
Message-ID: <2FE093E39DAE7D498A29AF6BE01F267B052B73AE@xmb-rtp-20c.amer.cisco.com> (raw)
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>
reply other threads:[~2009-05-19 17:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2FE093E39DAE7D498A29AF6BE01F267B052B73AE@xmb-rtp-20c.amer.cisco.com \
--to=nhennefe@cisco.com \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox