From: Frans Pop <elendil@planet.nl>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Mel Gorman <mel@skynet.ie>
Subject: Re: Memory management woes - order 1 allocation failures
Date: Fri, 26 Feb 2010 16:33:16 +0100 [thread overview]
Message-ID: <201002261633.17437.elendil@planet.nl> (raw)
In-Reply-To: <84144f021002260601o7ab345fer86b8bec12dbfc31e@mail.gmail.com>
On Friday 26 February 2010, Pekka Enberg wrote:
> > Isn't it a bit strange that cache claims so much memory that real
> > processes get into allocation failures?
>
> All of the failed allocations seem to be GFP_ATOMIC so it's not _that_
> strange.
It's still very ugly though. And I would say it should be unnecessary.
> Dunno if anything changed recently. What's the last known good kernel for
> you?
I've not used that box very intensively in the past, but I first saw the
allocation failure with aptitude with either .31 or .32. I would be
extremely surprised if I could reproduce the problem with .30.
And I have done large rsyncs to the box without any problems in the past,
but that must have been with .24 or so kernels.
It seems likely to me that it's related to all the other swap and
allocation issues we've been seeing after .30.
Thanks,
FJP
--
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-02-26 15:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 11:32 Frans Pop
2010-02-26 12:24 ` Frans Pop
2010-02-26 14:01 ` Pekka Enberg
2010-02-26 15:33 ` Frans Pop [this message]
2010-02-26 16:43 ` Christoph Lameter
2010-02-26 17:17 ` Pekka Enberg
2010-03-01 1:42 ` KOSAKI Motohiro
2010-03-02 17:26 ` Mel Gorman
2010-03-02 18:34 ` Alan Cox
2010-03-02 19:11 ` Mel Gorman
2010-03-02 19:29 ` Greg KH
2010-03-02 21:16 ` Mel Gorman
2010-03-02 22:17 ` Alan Cox
2010-03-02 22:29 ` Mel Gorman
2010-03-12 3:32 ` Frans Pop
2010-03-02 23:31 ` KOSAKI Motohiro
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=201002261633.17437.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
--cc=penberg@cs.helsinki.fi \
/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