[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090514205600.GA14741@elf.ucw.cz>
Date: Thu, 14 May 2009 22:56:00 +0200
From: Pavel Machek <pavel@....cz>
To: Christoph Lameter <cl@...ux-foundation.org>
Cc: David Rientjes <rientjes@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Nick Piggin <npiggin@...e.de>, Mel Gorman <mel@....ul.ie>,
Peter Ziljstra <a.p.ziljstra@...llo.nl>,
Dave Hansen <dave@...ux.vnet.ibm.com>,
San Mehat <san@...roid.com>, Arve Hj?nnev?g <arve@...roid.com>,
linux-kernel@...r.kernel.org
Subject: Re: Misleading OOM messages
On Thu 2009-05-14 15:46:50, Christoph Lameter wrote:
> On Thu, 14 May 2009, Pavel Machek wrote:
>
> > It can be 'low on memory' if you play with mlock() a bit.
>
> But that is a reclaim failure becuase of mlocking pages.
>
> > It is out of memory if you run out of swap (or have no swap to begin with).
>
> That is a swap config issue.
Well, many machines are _designed_ to run without swap. Swapping on
flash is considered bad.
> > I believe message is often correct. What message would you suggest?
>
> "Failure to reclaim memory"
That is not a helpful message, I'm afraid. What about
"Memory allocation failure" ?
"Out of memory, or failed to allocate memory due to temporary spike"?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists