| commit | 23baf831a32c04f9a968812511540b1b3e648bf5 | [log] [tgz] |
|---|---|---|
| author | Kirill A. Shutemov <[email protected]> | Wed Mar 15 14:31:33 2023 +0300 |
| committer | Andrew Morton <[email protected]> | Wed Apr 05 19:42:46 2023 -0700 |
| tree | fcaca52cefbef2707710ce057f58fb1c955a0559 | |
| parent | 61883d3c32418f16e35e030ca0cfd5d2de95a649 [diff] |
mm, treewide: redefine MAX_ORDER sanely MAX_ORDER currently defined as number of orders page allocator supports: user can ask buddy allocator for page order between 0 and MAX_ORDER-1. This definition is counter-intuitive and lead to number of bugs all over the kernel. Change the definition of MAX_ORDER to be inclusive: the range of orders user can ask from buddy allocator is 0..MAX_ORDER now. [[email protected]: fix min() warning] Link: https://lkml.kernel.org/r/20230315153800.32wib3n5rickolvh@box [[email protected]: fix another min_t warning] [[email protected]: fixups per Zi Yan] Link: https://lkml.kernel.org/r/[email protected] [[email protected]: fix underlining in docs] Link: https://lore.kernel.org/oe-kbuild-all/[email protected]/ Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Kirill A. Shutemov <[email protected]> Reviewed-by: Michael Ellerman <[email protected]> [powerpc] Cc: "Kirill A. Shutemov" <[email protected]> Cc: Zi Yan <[email protected]> Signed-off-by: Andrew Morton <[email protected]>