On 08/17/2016 11:14 AM, Ralf-Peter Rohbeck wrote:
On 16.08.2016 00:43, Michal Hocko wrote:
On Tue 16-08-16 09:32:46, Michal Hocko wrote:
On Mon 15-08-16 11:42:11, Ralf-Peter Rohbeck wrote:
This time the OOM killer hit much quicker. No btrfs balance, just compiling
the kernel with the new change did it.
Much smaller logs so I'm attaching them.
Just to clarify. You have added the trace_printk for
try_to_release_page, right? (after fixing it of course). If yes there is
no single mention of that path failing which would support Joonsoo's
theory... Could you try with his patch?
And then it would be great if you could test with the current linux-next
tree. Vlastimil has done some changes which might help. But even if they
don't then it would be better to add more changes on top of them.
Results with 4.8.0-rc2 are attached. OOM happened rather quickly.
4.8.0-rc2 is not "linux-next". What Michal meant is the linux-next git
(there's no tarball on kernel.org for it):
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Ralf-Peter
----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt.
--
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>