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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>