[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1007261510320.2993@chino.kir.corp.google.com>
Date: Mon, 26 Jul 2010 15:12:01 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: dave b <db.pub.mail@...il.com>
cc: Hugh Dickins <hughd@...gle.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Subject: Re: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels
On Tue, 27 Jul 2010, dave b wrote:
> Actually it turns out on 2.6.34.1 I can trigger this issue. What it
> really is, is that linux doesn't invoke the oom killer when it should
> and kill something off. This is *really* annoying.
>
I'm not exactly sure what you're referring to, it's been two months and
you're using a new kernel and now you're saying that the oom killer isn't
being utilized when the original problem statement was that it was killing
things inappropriately?
> I used the follow script - (on 2.6.34.1)
> cat ./scripts/disable_over_commit
> #!/bin/bash
> echo 2 > /proc/sys/vm/overcommit_memory
> echo 40 > /proc/sys/vm/dirty_ratio
> echo 5 > /proc/sys/vm/dirty_background_ratio
>
> And I was still able to reproduce this bug.
> Here is some c code to trigger the condition I am talking about.
>
>
> #include <stdlib.h>
> #include <stdio.h>
>
> int main(void)
> {
> while(1)
> {
> malloc(1000);
> }
>
> return 0;
> }
>
--
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