From: Jaewon Kim <jaewon31.kim@samsung.com>
To: akpm@linux-foundation.org
Cc: mhocko@suse.com, vbabka@suse.cz, minchan@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
jaewon31.kim@gmail.com, Jaewon Kim <jaewon31.kim@samsung.com>
Subject: [PATCH] mm: page_ext: allocate page extension though first PFN is invalid
Date: Tue, 07 Nov 2017 18:44:47 +0900 [thread overview]
Message-ID: <20171107094447.14763-1-jaewon31.kim@samsung.com> (raw)
In-Reply-To: <CGME20171107094311epcas1p4a5dd975d6e9f3618a26a0a5d68c68b55@epcas1p4.samsung.com>
online_page_ext and page_ext_init allocate page_ext for each section, but
they do not allocate if the first PFN is !pfn_present(pfn) or
!pfn_valid(pfn).
Though the first page is not valid, page_ext could be useful for other
pages in the section. But checking all PFNs in a section may be time
consuming job. Let's check each (section count / 16) PFN, then prepare
page_ext if any PFN is present or valid.
Signed-off-by: Jaewon Kim <jaewon31.kim@samsung.com>
---
mm/page_ext.c | 25 ++++++++++++++++++++++---
1 file changed, 22 insertions(+), 3 deletions(-)
diff --git a/mm/page_ext.c b/mm/page_ext.c
index 32f18911deda..634f9c5a8b9b 100644
--- a/mm/page_ext.c
+++ b/mm/page_ext.c
@@ -312,7 +312,17 @@ static int __meminit online_page_ext(unsigned long start_pfn,
}
for (pfn = start; !fail && pfn < end; pfn += PAGES_PER_SECTION) {
- if (!pfn_present(pfn))
+ unsigned long t_pfn = pfn;
+ bool present = false;
+
+ while (t_pfn < ALIGN(pfn + 1, PAGES_PER_SECTION)) {
+ if (pfn_present(t_pfn)) {
+ present = true;
+ break;
+ }
+ t_pfn = ALIGN(pfn + 1, PAGES_PER_SECTION >> 4);
+ }
+ if (!present)
continue;
fail = init_section_page_ext(pfn, nid);
}
@@ -391,8 +401,17 @@ void __init page_ext_init(void)
*/
for (pfn = start_pfn; pfn < end_pfn;
pfn = ALIGN(pfn + 1, PAGES_PER_SECTION)) {
-
- if (!pfn_valid(pfn))
+ unsigned long t_pfn = pfn;
+ bool valid = false;
+
+ while (t_pfn < ALIGN(pfn + 1, PAGES_PER_SECTION)) {
+ if (pfn_valid(t_pfn)) {
+ valid = true;
+ break;
+ }
+ t_pfn = ALIGN(pfn + 1, PAGES_PER_SECTION >> 4);
+ }
+ if (!valid)
continue;
/*
* Nodes's pfns can be overlapping.
--
2.13.0
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2017-11-07 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171107094311epcas1p4a5dd975d6e9f3618a26a0a5d68c68b55@epcas1p4.samsung.com>
2017-11-07 9:44 ` Jaewon Kim [this message]
2017-11-08 7:52 ` Joonsoo Kim
2017-11-08 13:33 ` Jaewon Kim
2017-11-09 4:33 ` Joonsoo Kim
[not found] <CGME20171102063347epcas2p2ce3e91597de3bf68e818130ea44ac769@epcas2p2.samsung.com>
2017-11-02 6:35 ` Jaewon Kim
2017-11-02 8:02 ` Michal Hocko
2017-11-06 22:30 ` Jaewon Kim
2017-11-07 7:47 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171107094447.14763-1-jaewon31.kim@samsung.com \
--to=jaewon31.kim@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=jaewon31.kim@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox