public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: werner <w.landgraf@ru.ru>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Hugh Dickins <hughd@google.com>,
	linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
	Rabin Vincent <rabin.vincent@stericsson.com>,
	Christian Bejram <christian.bejram@stericsson.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Anton Vorontsov <anton.vorontsov@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, rientjes@google.com
Subject: Re: v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1 sticks-and-crashs)
Date: Mon, 09 Apr 2012 21:51:58 -0400	[thread overview]
Message-ID: <4F83923E.6010802@redhat.com> (raw)
In-Reply-To: <web-723115389@zbackend1.aha.ru>

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

  reply	other threads:[~2012-04-10  1:52 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10  1:52 v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1 sticks-and-crashs) werner
2012-04-10  1:51 ` Rik van Riel [this message]
2012-04-10  2:13   ` werner
  -- strict thread matches above, loose matches on Subject: below --
2012-04-14 19:38 werner
2012-04-14 19:58 ` Rik van Riel
2012-04-14 21:03 ` Linus Torvalds
2012-04-10 12:53 werner
2012-04-09  7:01 werner
2012-04-09  6:52 werner
2012-04-09  2:42 Linus Torvalds
2012-04-09  2:50 ` Andrew Morton
2012-04-09  3:11   ` Linus Torvalds
2012-04-09  7:04     ` Sven Joachim
2012-04-09 15:24       ` Linus Torvalds
2012-04-09 15:43         ` Sven Joachim
2012-04-09 15:57       ` Rik van Riel
2012-04-09 16:19         ` Sven Joachim
2012-04-09 16:33           ` Rik van Riel
2012-04-09 17:00             ` Pekka Enberg
2012-04-09 17:19               ` Sven Joachim
2012-04-09 17:00             ` Sven Joachim
2012-04-09 17:20               ` Rik van Riel
2012-04-09 10:15     ` David Rientjes
2012-04-09 15:39       ` Linus Torvalds
2012-04-09 21:22         ` David Rientjes
2012-04-09 22:09           ` Linus Torvalds
2012-04-09 23:25             ` David Rientjes
2012-04-09 23:55               ` Linus Torvalds
2012-04-10  0:04                 ` David Rientjes
2012-04-14 20:50                 ` Srivatsa S. Bhat
     [not found]               ` <web-723076709@zbackend1.aha.ru>
     [not found]                 ` <alpine.DEB.2.00.1204091637280.21813@chino.kir.corp.google.com>
     [not found]                   ` <web-723082731@zbackend1.aha.ru>
     [not found]                     ` <alpine.DEB.2.00.1204091707580.21813@chino.kir.corp.google.com>
2012-04-10  7:09                       ` werner
2012-04-10  7:10                       ` werner
2012-04-09 22:13           ` Colin Cross
2012-04-09 22:21             ` Greg Kroah-Hartman
2012-04-09 22:44               ` john stultz
2012-04-09 22:30             ` Linus Torvalds
2012-04-09 23:37             ` David Rientjes
2012-04-10  0:23               ` Colin Cross
2012-04-10  0:32                 ` David Rientjes
2012-04-10  1:21                   ` Colin Cross
2012-04-10  1:33                     ` David Rientjes
2012-04-10  1:37                       ` Colin Cross

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=4F83923E.6010802@redhat.com \
    --to=riel@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton.vorontsov@linaro.org \
    --cc=christian.bejram@stericsson.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rabin.vincent@stericsson.com \
    --cc=rientjes@google.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=w.landgraf@ru.ru \
    /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