On Fri, Sep 26, 2014 at 10:08:54AM +0000, Gore, Tim wrote: > I don't think so. This is really just about the Android low memory killer having > Different goals to kswapd. Kswapd tries to keep a certain amount of free memory > so that the kernel can run smoothly. On Android the lowmemorykiller attempts > to maintain somewhat higher levels of free memory by killing off processes, > because the user is not expected to ever close anything and expects new > applications to open quickly. So if you put the memory under pressure the > Android low memory killer will inevitably look for something to kill, and if > your test is the only thing running its toast. The linux oom killer is still there, > but is never needed on Android because the lowmemorykiller gets there first. Though I think the interaction between lowmemkiller and i915 is broken, I do agree that we need to run our swap tests and that to do so we need to disable lowmemkiller. I would prefer it if only the swap-thrash tests disabled the lowmemkiller though, as I think we still need to test integration behaviour and if lowmemkiller starts killing tests that we think should be well within the limits, that is likely to be our bug. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
