From: David Rientjes <rientjes@google.com>
To: Mahmood Naderan <nt_mahmood@yahoo.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
"\"\"linux-kernel@vger.kernel.org\"\""
<linux-kernel@vger.kernel.org>,
"\"linux-mm@kvack.org\"" <linux-mm@kvack.org>
Subject: Re: running of out memory => kernel crash
Date: Thu, 11 Aug 2011 00:13:10 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1108110010220.23622@chino.kir.corp.google.com> (raw)
In-Reply-To: <1313046422.18195.YahooMailNeo@web111711.mail.gq1.yahoo.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 853 bytes --]
On Thu, 11 Aug 2011, Mahmood Naderan wrote:
> >The default behavior is to kill all eligible and unkillable threads until
> >there are none left to sacrifice (i.e. all kthreads and OOM_DISABLE).
>
> In a simple test with virtualbox, I reduced the amount of ram to 300MB.
> Then I ran "swapoff -a" and opened some applications. I noticed that the free
> spaces is kept around 2-3MB and "kswapd" is running. Also I saw that disk
> activity was very high.
> That mean although "swap" partition is turned off, "kswapd" was trying to do
> something. I wonder how that behavior can be explained?
>
Despite it's name, kswapd is still active, it's trying to reclaim memory
to prevent having to kill a process as the last resort.
If /proc/sys/vm/panic_on_oom is not set, as previously mentioned, then
we'll need the kernel log to diagnose this further.
next prev parent reply other threads:[~2011-08-11 7:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1312872786.70934.YahooMailNeo@web111712.mail.gq1.yahoo.com>
2011-08-09 7:06 ` Randy Dunlap
[not found] ` <1312874259.89770.YahooMailNeo@web111704.mail.gq1.yahoo.com>
2011-08-09 16:03 ` David Rientjes
2011-08-10 8:14 ` Mahmood Naderan
2011-08-11 4:09 ` David Rientjes
2011-08-11 7:07 ` Mahmood Naderan
2011-08-11 7:13 ` David Rientjes [this message]
2011-08-11 8:02 ` Mahmood Naderan
2011-08-11 12:47 ` Denys Vlasenko
2011-08-11 15:13 ` Mahmood Naderan
2011-08-11 17:38 ` Denys Vlasenko
2011-08-17 8:50 ` Mahmood Naderan
2011-08-18 2:18 ` Pavel Ivanov
2011-08-18 12:44 ` Denys Vlasenko
2011-08-18 14:26 ` Pavel Ivanov
2011-08-18 22:25 ` Denys Vlasenko
2011-08-19 19:21 ` David Rientjes
2011-08-19 19:29 ` Bryan Donlan
2011-08-19 21:19 ` Chris Friesen
2011-08-19 21:38 ` Alan Cox
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=alpine.DEB.2.00.1108110010220.23622@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nt_mahmood@yahoo.com \
--cc=rdunlap@xenotime.net \
/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