From: David Hildenbrand <david@redhat.com>
To: Baoquan He <bhe@redhat.com>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, mhocko@suse.com,
richard.weiyang@gmail.com, dan.j.williams@intel.com
Subject: Re: [PATCH v4 4/5] mm/sparse.c: add note about only VMEMMAP supporting sub-section hotplug
Date: Thu, 12 Mar 2020 14:45:16 +0100 [thread overview]
Message-ID: <6c405f10-be9d-ca0e-3cc0-70a7bf24cbfa@redhat.com> (raw)
In-Reply-To: <20200312124414.439-5-bhe@redhat.com>
On 12.03.20 13:44, Baoquan He wrote:
> And tell check_pfn_span() gating the porper alignment and size of
> hot added memory region.
>
> And also move the code comments from inside section_deactivate()
> to being above it. The code comments are reasonable for the whole
> function, and the moving makes code cleaner.
>
> Signed-off-by: Baoquan He <bhe@redhat.com>
> Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> mm/sparse.c | 38 +++++++++++++++++++++-----------------
> 1 file changed, 21 insertions(+), 17 deletions(-)
>
> diff --git a/mm/sparse.c b/mm/sparse.c
> index 117fe4554c38..f02a524e17d1 100644
> --- a/mm/sparse.c
> +++ b/mm/sparse.c
> @@ -771,6 +771,22 @@ static bool is_subsection_map_empty(struct mem_section *ms)
> }
> #endif
>
> +/*
> + * To deactivate a memory region, there are 3 cases to handle across
> + * two configurations (SPARSEMEM_VMEMMAP={y,n}):
> + *
> + * 1. deactivation of a partial hot-added section (only possible in
> + * the SPARSEMEM_VMEMMAP=y case).
> + * a) section was present at memory init.
> + * b) section was hot-added post memory init.
> + * 2. deactivation of a complete hot-added section.
> + * 3. deactivation of a complete section from memory init.
> + *
> + * For 1, when subsection_map does not empty we will not be freeing the
> + * usage map, but still need to free the vmemmap range.
> + *
> + * For 2 and 3, the SPARSEMEM_VMEMMAP={y,n} cases are unified
> + */
> static void section_deactivate(unsigned long pfn, unsigned long nr_pages,
> struct vmem_altmap *altmap)
> {
> @@ -781,23 +797,7 @@ static void section_deactivate(unsigned long pfn, unsigned long nr_pages,
>
> if (clear_subsection_map(pfn, nr_pages))
> return;
> - /*
> - * There are 3 cases to handle across two configurations
> - * (SPARSEMEM_VMEMMAP={y,n}):
> - *
> - * 1/ deactivation of a partial hot-added section (only possible
> - * in the SPARSEMEM_VMEMMAP=y case).
> - * a/ section was present at memory init
> - * b/ section was hot-added post memory init
> - * 2/ deactivation of a complete hot-added section
> - * 3/ deactivation of a complete section from memory init
> - *
> - * For 1/, when subsection_map does not empty we will not be
> - * freeing the usage map, but still need to free the vmemmap
> - * range.
> - *
> - * For 2/ and 3/ the SPARSEMEM_VMEMMAP={y,n} cases are unified
> - */
> +
> empty = is_subsection_map_empty(ms);
> if (empty) {
> unsigned long section_nr = pfn_to_section_nr(pfn);
> @@ -905,6 +905,10 @@ static struct page * __meminit section_activate(int nid, unsigned long pfn,
> *
> * This is only intended for hotplug.
> *
> + * Note that only VMEMMAP supports sub-section aligned hotplug,
> + * the proper alignment and size are gated by check_pfn_span().
> + *
> + *
> * Return:
> * * 0 - On success.
> * * -EEXIST - Section has been present.
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-03-12 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 12:44 [PATCH v4 0/5] mm/hotplug: Only use subsection map for VMEMMAP Baoquan He
2020-03-12 12:44 ` [PATCH v4 1/5] mm/sparse.c: introduce new function fill_subsection_map() Baoquan He
2020-03-12 13:30 ` Pankaj Gupta
2020-03-12 12:44 ` [PATCH v4 2/5] mm/sparse.c: introduce a new function clear_subsection_map() Baoquan He
2020-03-12 13:26 ` Pankaj Gupta
2020-03-12 12:44 ` [PATCH v4 3/5] mm/sparse.c: only use subsection map in VMEMMAP case Baoquan He
2020-03-12 12:44 ` [PATCH v4 4/5] mm/sparse.c: add note about only VMEMMAP supporting sub-section hotplug Baoquan He
2020-03-12 13:45 ` David Hildenbrand [this message]
2020-03-12 12:44 ` [PATCH v4 5/5] mm/sparse.c: move subsection_map related functions together 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=6c405f10-be9d-ca0e-3cc0-70a7bf24cbfa@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=richard.weiyang@gmail.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