On Thu, 2 Jan 2014, Dave Hansen wrote: > > The default value of min_free_kbytes depends on the implementation of the > > VM regardless of any config options that you may have enabled. We don't > > specify what the non-thp default is in the kernel log, so why do we need > > to specify what the thp default is? > > Let's say enabling THP made my system behave badly. How do I get it > back to the state before I enabled THP? The user has to have gone and > recorded what their min_free_kbytes was before turning THP on in order > to get it back to where it was. Folks also have to either plan in > advance (archiving *ALL* the sysctl settings), somehow *know* somehow > that THP can affect min_free_kbytes, or just plain be clairvoyant. > How is this different from some initscript changing the value? We should either specify that min_free_kbytes changed from its default, which may change from kernel version to kernel version itself, in all cases or just leave it as it currently is. There's no reason to special-case thp in this way if there are other ways to change the value. -- 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>