[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1511594447-3836-1-git-send-email-chenjiankang1@huawei.com>
Date: Sat, 25 Nov 2017 15:20:47 +0800
From: JianKang Chen <chenjiankang1@...wei.com>
To: <akpm@...ux-foundation.org>, <mhocko@...e.com>,
<mgorman@...hsingularity.net>, <hillf.zj@...baba-inc.com>
CC: <hannes@...xchg.org>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, <xieyisheng1@...wei.com>,
<guohanjun@...wei.com>, <wangkefeng.wang@...wei.com>,
<chenjiankang1@...wei.com>
Subject: [PATCH resend] mm/page_alloc: fix comment is __get_free_pages
From: Jiankang Chen <chenjiankang1@...wei.com>
__get_free_pages will return an 64bit address in 64bit System
like arm64 or x86_64. And this comment really confuse new bigenner of
mm.
Signed-off-by: Jiankang Chen <chenjiankang1@...wei.com>
---
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 77e4d3c..5a7c432 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -4240,7 +4240,7 @@ unsigned long __get_free_pages(gfp_t gfp_mask, unsigned int order)
struct page *page;
/*
- * __get_free_pages() returns a 32-bit address, which cannot represent
+ * __get_free_pages() returns a virtual address, which cannot represent
* a highmem page
*/
VM_BUG_ON((gfp_mask & __GFP_HIGHMEM) != 0);
--
1.7.12.4
Powered by blists - more mailing lists