From: Christoph Lameter <cl@linux.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: Pekka Enberg <penberg@kernel.org>,
Mikael Abrahamsson <swmike@swm.pp.se>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Mel Gorman <mel@csn.ul.ie>
Subject: Re: 2.6.34.1 page allocation failure
Date: Tue, 24 Aug 2010 12:13:23 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1008241210570.3695@router.home> (raw)
In-Reply-To: <4C72F7C6.3020109@hardwarefreak.com>
On Mon, 23 Aug 2010, Stan Hoeppner wrote:
> Should I be using SLUB instead? Any downsides to SLUB on an old and
> slow (500 MHz) single core dual CPU box with <512MB RAM?
SLUB has a smaller memory footprint so you may come out ahead for
such a small system in particular.
> Also, what is the impact of these oopses? Despite the entries in dmesg,
> the system "seems" to be running ok. Or is this simply the calm before
> the impending storm?
The system does not guarantee that GFP_ATOMIC allocation succeed so any
caller must provide logic to fall back if no memory is allocated. So the
effect may just be that certain OS operations have to be retried.
--
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>
next prev parent reply other threads:[~2010-08-24 17:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C70BFF3.8030507@hardwarefreak.com>
2010-08-22 6:47 ` Mikael Abrahamsson
2010-08-22 19:51 ` Pekka Enberg
2010-08-22 22:40 ` Christoph Lameter
2010-08-23 9:37 ` Pekka Enberg
2010-08-23 22:35 ` Stan Hoeppner
2010-08-24 17:13 ` Christoph Lameter [this message]
2010-08-24 18:03 ` Pekka Enberg
2010-08-24 19:08 ` Stan Hoeppner
2010-08-24 19:21 ` Mikael Abrahamsson
2010-08-29 10:49 ` Pekka Enberg
2010-08-29 12:38 ` Mikael Abrahamsson
2010-08-29 13:17 ` Pekka Enberg
2010-08-29 15:37 ` Mikael Abrahamsson
2010-08-31 20:28 ` Mikael Abrahamsson
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.1008241210570.3695@router.home \
--to=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=penberg@kernel.org \
--cc=stan@hardwarefreak.com \
--cc=swmike@swm.pp.se \
/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