From: Baoquan He <bhe@redhat.com>
To: Oscar Salvador <osalvador@techadventures.net>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
dave.hansen@intel.com, pagupta@redhat.com, linux-mm@kvack.org,
kirill.shutemov@linux.intel.com
Subject: Re: [PATCH v5 2/4] mm/sparsemem: Defer the ms->section_mem_map clearing
Date: Thu, 28 Jun 2018 06:59:45 +0800 [thread overview]
Message-ID: <20180627225945.GD8970@localhost.localdomain> (raw)
In-Reply-To: <20180627095439.GA5924@techadventures.net>
On 06/27/18 at 11:54am, Oscar Salvador wrote:
> On Wed, Jun 27, 2018 at 09:31:14AM +0800, Baoquan He wrote:
> > In sparse_init(), if CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y, system
> > will allocate one continuous memory chunk for mem maps on one node and
> > populate the relevant page tables to map memory section one by one. If
> > fail to populate for a certain mem section, print warning and its
> > ->section_mem_map will be cleared to cancel the marking of being present.
> > Like this, the number of mem sections marked as present could become
> > less during sparse_init() execution.
> >
> > Here just defer the ms->section_mem_map clearing if failed to populate
> > its page tables until the last for_each_present_section_nr() loop. This
> > is in preparation for later optimizing the mem map allocation.
> >
> > Signed-off-by: Baoquan He <bhe@redhat.com>
> > ---
> > mm/sparse-vmemmap.c | 1 -
> > mm/sparse.c | 12 ++++++++----
> > 2 files changed, 8 insertions(+), 5 deletions(-)
> >
> > diff --git a/mm/sparse-vmemmap.c b/mm/sparse-vmemmap.c
> > index bd0276d5f66b..640e68f8324b 100644
> > --- a/mm/sparse-vmemmap.c
> > +++ b/mm/sparse-vmemmap.c
> > @@ -303,7 +303,6 @@ void __init sparse_mem_maps_populate_node(struct page **map_map,
> > ms = __nr_to_section(pnum);
> > pr_err("%s: sparsemem memory map backing failed some memory will not be available\n",
> > __func__);
> > - ms->section_mem_map = 0;
>
> Since we are deferring the clearing of section_mem_map, I guess we do not need
>
> struct mem_section *ms;
> ms = __nr_to_section(pnum);
>
> anymore, right?
Right, good catch, thanks.
I will post a new round to fix this.
>
> > }
> >
> > if (vmemmap_buf_start) {
> > diff --git a/mm/sparse.c b/mm/sparse.c
> > index 6314303130b0..71ad53da2cd1 100644
> > --- a/mm/sparse.c
> > +++ b/mm/sparse.c
> > @@ -451,7 +451,6 @@ void __init sparse_mem_maps_populate_node(struct page **map_map,
> > ms = __nr_to_section(pnum);
> > pr_err("%s: sparsemem memory map backing failed some memory will not be available\n",
> > __func__);
> > - ms->section_mem_map = 0;
>
> The same goes here.
>
>
>
> --
> Oscar Salvador
> SUSE L3
next prev parent reply other threads:[~2018-06-27 22:59 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 ` [PATCH v5 1/4] mm/sparse: Add a static variable nr_present_sections Baoquan He
2018-06-28 3:10 ` 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 [this message]
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=20180627225945.GD8970@localhost.localdomain \
--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=osalvador@techadventures.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.