[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090514213403.GB14741@elf.ucw.cz>
Date: Thu, 14 May 2009 23:34:03 +0200
From: Pavel Machek <pavel@....cz>
To: Christoph Lameter <cl@...ux-foundation.org>
Cc: Dave Hansen <dave@...ux.vnet.ibm.com>,
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>,
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 17:30:02, Christoph Lameter wrote:
> On Thu, 14 May 2009, Dave Hansen wrote:
>
> > - printk(KERN_ERR "%s: kill process %d (%s) score %li or a child\n",
> > + printk(KERN_ERR "No available memory %s: "
> > + "kill process %d (%s) score %li or a child\n",
> > message, task_pid_nr(p), p->comm, points);
>
> "No available memory" still suggests that plugging in more memory is the
> right solution.
And... on correctly working kernel, it is, right?
If you have no swap space and too many applications, you plug more
memory. (Or invent some swap).
If you misconfigured cgroups, you give more memory to them.
If your applications mlocked 900MB and you have 1GB, you need to plug
more memory.
So... when is plugging more memory _not_ valid answer? AFAICT it is
when it is some kernel problem, resulting in memory not being
reclaimed fast enough....
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