* Kirill A. Shutemov <kirill@xxxxxxxxxxxxx> wrote: > > Or, could we keep MAX_PHYSMEM_BITS constant, and introduce a _different_ constant > > that is dynamic, and which could be used in the cases where the 5-level paging > > config causes too much memory footprint in the common 4-level paging case? > > This is more labor intensive case with unclear benefit. > > Dynamic MAX_PHYSMEM_BITS doesn't cause any issue in waste majority of > cases. Almost nothing uses it - and even in those few cases it caused problems. Making a variable that 'looks' like a constant macro dynamic in a rare Kconfig scenario is asking for trouble. Thanks, Ingo -- 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>
