From: Mike Galbraith <efault@gmx.de>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: swapping and oom-killer: gfp_mask=0x201d2, order=0
Date: Fri, 12 May 2006 07:48:30 +0200 [thread overview]
Message-ID: <1147412910.8432.14.camel@homer> (raw)
In-Reply-To: <200605111514.45503.a1426z@gawab.com>
On Thu, 2006-05-11 at 15:14 +0300, Al Boldi wrote:
> The current mm behaviour in 2.6, during physical memory exhaustion, expresses
> itself as an oom-killing spree, while the kernel could have resorted to
> swapping.
>
> Is there a reason why oom-killing is currently preferred over swapping?
Looks to me like you booted with mem=8m, and these allocations are
failing because every page the page allocator tried to issue were marked
as being reserved. The SysRq-M output shows that it did try to swap as
it limped along.
My box won't get past a black screen hang with less than mem=24m, so I'm
kinda surprised you got far enough to even add swap.
-Mike
next prev parent reply other threads:[~2006-05-12 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 12:14 swapping and oom-killer: gfp_mask=0x201d2, order=0 Al Boldi
2006-05-12 5:48 ` Mike Galbraith [this message]
2006-05-12 12:17 ` Al Boldi
2006-05-12 15:31 ` Mike Galbraith
2006-05-13 12:11 ` Al Boldi
2006-05-13 12:54 ` Mike Galbraith
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=1147412910.8432.14.camel@homer \
--to=efault@gmx.de \
--cc=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.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