On 13/11/13 13:19, Cyrill Gorcunov wrote:
On Wed, Nov 13, 2013 at 12:35:34PM +0000, Alin Dobre wrote:
On 13/11/13 12:09, Cyrill Gorcunov wrote:
On Wed, Nov 13, 2013 at 11:18:26AM +0000, Alin Dobre wrote:
The above traces seem similar with the ones that were reported by
Dave couple of months ago in the LKML thread
https://lkml.org/lkml/2013/8/7/27.
Any further thoughts on why this happens?
Dave's report has been addressed in commit 6dec97dc9, which is
in 3.11, also you're to have CONFIG_MEM_SOFT_DIRTY=y to trigger
it in former case.
Thanks a lot, Cyrill. That's a really good piece of information, we
must have missed it although it was clearly there.
In the meantime, we will try to reproduce the problem and see if
this fix together with CONFIG_MEM_SOFT_DIRTY=y works for our OOM
kills also.
Hi Alin, actually if your config has no CONFIG_MEM_SOFT_DIRTY=y
then the fix won't help, it might be some different issue (Dave
has been testing the kernel with soft-dirty option set). But of
course I don't mind if you test the kernel with soft dirty option
turned on.
Thanks Cyrill! We'll test the kernel anyway to try and reproduce the
mass oom killing, so we'll see from there.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>