The patch titled
Subject: mm/vmalloc.c: use "high-order" in description non 0-order pages
has been added to the -mm mm-unstable branch. Its filename is
mm-vmallocc-use-high-order-in-description-non-0-order-pages.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-vmallocc-use-high-order-in-description-non-0-order-pages.patch
This patch will later appear in the mm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days
------------------------------------------------------
From: "Uladzislau Rezki (Sony)" <urezki@xxxxxxxxx>
Subject: mm/vmalloc.c: use "high-order" in description non 0-order pages
Date: Fri, 6 Sep 2024 11:50:49 +0200
In many places, in the comments, we use both "higher-order" and
"high-order" to describe the non 0-order pages. That is confusing,
because a "higher-order" statement does not reflect what it is compared
with.
Link: https://lkml.kernel.org/r/20240906095049.3486-1-urezki@xxxxxxxxx
Signed-off-by: Uladzislau Rezki (Sony) <urezki@xxxxxxxxx>
Suggested-by: Baoquan He <bhe@xxxxxxxxxx>
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Cc: Michal Hocko <mhocko@xxxxxxxx>
Cc: Oleksiy Avramchenko <oleksiy.avramchenko@xxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/vmalloc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/mm/vmalloc.c~mm-vmallocc-use-high-order-in-description-non-0-order-pages
+++ a/mm/vmalloc.c
@@ -3589,7 +3589,7 @@ vm_area_alloc_pages(gfp_t gfp, int nid,
break;
/*
- * Higher order allocations must be able to be treated as
+ * High-order allocations must be able to be treated as
* independent small pages by callers (as they can with
* small-page vmallocs). Some drivers do their own refcounting
* on vmalloc_to_page() pages, some use page->mapping,
@@ -3652,7 +3652,7 @@ static void *__vmalloc_area_node(struct
page_order = vm_area_page_order(area);
/*
- * Higher order nofail allocations are really expensive and
+ * High-order nofail allocations are really expensive and
* potentially dangerous (pre-mature OOM, disruptive reclaim
* and compaction etc.
*
_
Patches currently in -mm which might be from urezki@xxxxxxxxx are
mm-vmallocc-use-high-order-in-description-non-0-order-pages.patch
