New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 725121 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

try harder to turn on CONFIG_COMPACTION

Project Member Reported by semenzato@chromium.org, May 22 2017

Issue description

We're seeing OOM kills from fork(), which requires 4 contiguous pages (order 2), with plenty of available RAM and swap, but with RAM too fragmented to satisfy the request.

We tried turning it on already but it correlated with a couple of problems.  See issue 603594 (April 2016) where we reverted the turn-ons.  It's also possible that issue 585552 is related to compaction.  Finally,  issue 586052  also involves compaction but only in 3.8 kernels.  The highest interest at this time is 3.18.


 
Status: WontFix (was: Untriaged)
It looks like we've actually been running with CONFIG_COMPACTION for a little while now.  It was turned on by "transparent huge pages".

For amd64, this was turned on in June of 2016.  crosreview.com/347467
For arm32, this was turned on in Feb of 2017.  crosreview.com/350895

BTW: filed bug #725574 to make our kernel configs a little less confusing here.

Sign in to add a comment