[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F83923E.6010802@redhat.com>
Date: Mon, 09 Apr 2012 21:51:58 -0400
From: Rik van Riel <riel@...hat.com>
To: werner <w.landgraf@...ru>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Hugh Dickins <hughd@...gle.com>, linux-kernel@...r.kernel.org,
Oleg Nesterov <oleg@...hat.com>,
Rabin Vincent <rabin.vincent@...ricsson.com>,
Christian Bejram <christian.bejram@...ricsson.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Anton Vorontsov <anton.vorontsov@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stable@...r.kernel.org, rientjes@...gle.com
Subject: Re: v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1 sticks-and-crashs)
On 04/09/2012 09:52 PM, werner wrote:
> At least until now, and also tested hard by starting and stopping
> several memory-consuming operations, I'm happy to can inform that the
> computer didnt yet crash again, and that also slownessnesses what I
> observed under 3.3 (but without crashs) don't occur
That could be due to a few VM patches which I wrote, that
went in through -mm.
I am very interested in whether people do find a way to
break the VM with those patches, in ways that used to work
before.
If you find any, please let me know so I can fix them
before the 3.4 kernel comes out.
If everything you try works better than before, I'm not
going to complain about good news :)
--
All rights reversed
--
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