Re: OOM-Killer kills too much with 2.6.32.2

From: Michael Reinelt
Date: Tue Jan 26 2010 - 09:10:16 EST




Chris Wilson schrieb:
> On Tue, 26 Jan 2010 22:03:06 +0900, KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx> wrote:
>> Please consider to revert such commit at once. Lots people reported
>> the same issue.
>> I really hope to stop bug report storm.
>
> Your CC did not reference the problem that you were discussing, nor that
> it is even easier to trigger an OOM without the shrinker. Memory
> exhaustion due to the excess usage of surfaces from userspace is not a new
> issuer. So what is the problem you have encountered and how does running
> the OOM killer earlier fix the issue of triggering the OOM killer?
>

To end this discussion: I just had a OOM with the GEM / shmem partial revert patch from Motohiro :-(

Unfortunately without Motohiro's oom-debug patch applied :-(

as a non-git-user I have to manually patch memory.c, but I hope I can get things right. I will provide results ASAP.



--
Michael Reinelt <michael@xxxxxxxxxxxxx>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/