On Wed, Apr 19, 2017 at 01:13:43PM +0200, Michal Hocko wrote: > On Tue 18-04-17 14:47:32, David Rientjes wrote: > [...] > > I think the debug_guardpage_minorder() check makes sense for failed > > allocations because we are essentially removing memory from the system for > > debug, failed allocations as a result of low on memory or fragmentation > > aren't concerning if we are removing memory from the system. > > I really fail to see how this is any different from booting with > mem=$SIZE to reduce the amount of available memory. mem= shrink upper memory limit, debug_guardpage_minorder= fragments available physical memory (deliberately to catch unintended access). Stanislaw -- 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>
