From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
dave.hansen@intel.com, pagupta@redhat.com
Cc: linux-mm@kvack.org, kirill.shutemov@linux.intel.com,
Baoquan He <bhe@redhat.com>
Subject: [PATCH v5 1/4] mm/sparse: Add a static variable nr_present_sections
Date: Wed, 27 Jun 2018 09:31:13 +0800 [thread overview]
Message-ID: <20180627013116.12411-2-bhe@redhat.com> (raw)
In-Reply-To: <20180627013116.12411-1-bhe@redhat.com>
It's used to record how many memory sections are marked as present
during system boot up, and will be used in the later patch.
Signed-off-by: Baoquan He <bhe@redhat.com>
---
mm/sparse.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/mm/sparse.c b/mm/sparse.c
index f13f2723950a..6314303130b0 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -200,6 +200,12 @@ static inline int next_present_section_nr(int section_nr)
(section_nr <= __highest_present_section_nr)); \
section_nr = next_present_section_nr(section_nr))
+/*
+ * Record how many memory sections are marked as present
+ * during system bootup.
+ */
+static int __initdata nr_present_sections;
+
/* Record a memory area against a node. */
void __init memory_present(int nid, unsigned long start, unsigned long end)
{
@@ -229,6 +235,7 @@ void __init memory_present(int nid, unsigned long start, unsigned long end)
ms->section_mem_map = sparse_encode_early_nid(nid) |
SECTION_IS_ONLINE;
section_mark_present(ms);
+ nr_present_sections++;
}
}
}
--
2.13.6
next prev parent reply other threads:[~2018-06-27 1:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 1:31 [PATCH v5 0/4] mm/sparse: Optimize memmap allocation during sparse_init() Baoquan He
2018-06-27 1:31 ` Baoquan He [this message]
2018-06-28 3:10 ` [PATCH v5 1/4] mm/sparse: Add a static variable nr_present_sections Pavel Tatashin
2018-06-27 1:31 ` [PATCH v5 2/4] mm/sparsemem: Defer the ms->section_mem_map clearing Baoquan He
2018-06-27 9:54 ` Oscar Salvador
2018-06-27 22:59 ` Baoquan He
2018-06-28 3:11 ` Pavel Tatashin
2018-06-27 1:31 ` [PATCH v5 3/4] mm/sparse: Add a new parameter 'data_unit_size' for alloc_usemap_and_memmap Baoquan He
2018-06-28 3:14 ` Pavel Tatashin
2018-06-28 6:57 ` Baoquan He
2018-06-27 1:31 ` [PATCH v5 4/4] mm/sparse: Optimize memmap allocation during sparse_init() Baoquan He
2018-06-28 3:19 ` Pavel Tatashin
2018-06-28 6:39 ` Baoquan He
2018-06-29 17:16 ` Dave Hansen
2018-06-29 17:48 ` Pavel Tatashin
2018-06-29 17:52 ` Dave Hansen
2018-06-29 18:01 ` Pavel Tatashin
2018-06-29 18:56 ` Dave Hansen
2018-06-29 18:59 ` Pavel Tatashin
2018-06-27 1:47 ` [PATCH v5 0/4] " Baoquan He
2018-06-27 17:47 ` Pavel Tatashin
2018-06-27 23:39 ` Baoquan He
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=20180627013116.12411-2-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pagupta@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).