Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
mm: vmscan: do not keep kswapd looping forever due to individual unco…
…mpactable zones When a zone meets its high watermark and is compactable in case of higher order allocations, it contributes to the percentage of the node's memory that is considered balanced. This requirement, that a node be only partially balanced, came about when kswapd was desparately trying to balance tiny zones when all bigger zones in the node had plenty of free memory. Arguably, the same should apply to compaction: if a significant part of the node is balanced enough to run compaction, do not get hung up on that tiny zone that might never get in shape. When the compaction logic in kswapd is reached, we know that at least 25% of the node's memory is balanced properly for compaction (see zone_balanced and pgdat_balanced). Remove the individual zone checks that restart the kswapd cycle. Otherwise, we may observe more endless looping in kswapd where the compaction code loops back to reclaim because of a single zone and reclaim does nothing because the node is considered balanced overall. See for example https://bugzilla.redhat.com/show_bug.cgi?id=866988 Signed-off-by: Johannes Weiner <[email protected]> Reported-and-tested-by: Thorsten Leemhuis <[email protected]> Reported-by: Jiri Slaby <[email protected]> Tested-by: John Ellson <[email protected]> Tested-by: Zdenek Kabelac <[email protected]> Tested-by: Bruno Wolff III <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
- Loading branch information