mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-10-14 20:46:39 +00:00
23baf831a3
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. [kirill@shutemov.name: fix min() warning] Link: https://lkml.kernel.org/r/20230315153800.32wib3n5rickolvh@box [akpm@linux-foundation.org: fix another min_t warning] [kirill@shutemov.name: fixups per Zi Yan] Link: https://lkml.kernel.org/r/20230316232144.b7ic4cif4kjiabws@box.shutemov.name [akpm@linux-foundation.org: fix underlining in docs] Link: https://lore.kernel.org/oe-kbuild-all/202303191025.VRCTk6mP-lkp@intel.com/ Link: https://lkml.kernel.org/r/20230315113133.11326-11-kirill.shutemov@linux.intel.com Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Reviewed-by: Michael Ellerman <mpe@ellerman.id.au> [powerpc] Cc: "Kirill A. Shutemov" <kirill@shutemov.name> Cc: Zi Yan <ziy@nvidia.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> |
||
|---|---|---|
| .. | ||
| hash_4k.c | ||
| hash_64k.c | ||
| hash_hugepage.c | ||
| hash_native.c | ||
| hash_pgtable.c | ||
| hash_tlb.c | ||
| hash_utils.c | ||
| hugetlbpage.c | ||
| internal.h | ||
| iommu_api.c | ||
| Makefile | ||
| mmu_context.c | ||
| pgtable.c | ||
| pkeys.c | ||
| radix_hugetlbpage.c | ||
| radix_pgtable.c | ||
| radix_tlb.c | ||
| slb.c | ||
| slice.c | ||
| subpage_prot.c | ||
| trace.c | ||