On Wed, 19 Apr 2017, Stanislaw Gruszka wrote: > mem= shrink upper memory limit, debug_guardpage_minorder= fragments > available physical memory (deliberately to catch unintended access). > Agreed, and allocation failure warnings don't need to cache the mem= kernel parameter and determine the difference between true system RAM and configured system RAM to try to determine if a warning is appropriate lol. Let's please leave the check as Stanislaw has repeatedly requested. -- 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>
