From: David Hildenbrand <david@redhat.com>
To: Dong Aisheng <dongas86@gmail.com>
Cc: Dong Aisheng <aisheng.dong@nxp.com>,
linux-mm@kvack.org, open list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Young <dyoung@redhat.com>, Baoquan He <bhe@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
kexec@lists.infradead.org
Subject: Re: [PATCH V2 4/6] mm: rename the global section array to mem_sections
Date: Tue, 1 Jun 2021 10:40:09 +0200 [thread overview]
Message-ID: <f7f77368-72cf-e15d-cc3c-b0ddf86e14fd@redhat.com> (raw)
In-Reply-To: <CAA+hA=Ss4j8qeoe7RtDJ14nuqy+TpOk2qi-A9+YN6=2y8c_CGg@mail.gmail.com>
On 01.06.21 10:37, Dong Aisheng wrote:
> On Tue, Jun 1, 2021 at 4:22 PM David Hildenbrand <david@redhat.com> wrote:
>>
>> On 31.05.21 11:19, Dong Aisheng wrote:
>>> In order to distinguish the struct mem_section for a better code
>>> readability and align with kernel doc [1] name below, change the
>>> global mem section name to 'mem_sections' from 'mem_section'.
>>>
>>> [1] Documentation/vm/memory-model.rst
>>> "The `mem_section` objects are arranged in a two-dimensional array
>>> called `mem_sections`."
>>>
>>> Cc: Andrew Morton <akpm@linux-foundation.org>
>>> Cc: Dave Young <dyoung@redhat.com>
>>> Cc: Baoquan He <bhe@redhat.com>
>>> Cc: Vivek Goyal <vgoyal@redhat.com>
>>> Cc: kexec@lists.infradead.org
>>> Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
>>> ---
>>> v1->v2:
>>> * no changes
>>> ---
>>> include/linux/mmzone.h | 10 +++++-----
>>> kernel/crash_core.c | 4 ++--
>>> mm/sparse.c | 16 ++++++++--------
>>> 3 files changed, 15 insertions(+), 15 deletions(-)
>>>
>>> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
>>> index a6bfde85ddb0..0ed61f32d898 100644
>>> --- a/include/linux/mmzone.h
>>> +++ b/include/linux/mmzone.h
>>> @@ -1302,9 +1302,9 @@ struct mem_section {
>>> #define SECTION_ROOT_MASK (SECTIONS_PER_ROOT - 1)
>>>
>>> #ifdef CONFIG_SPARSEMEM_EXTREME
>>> -extern struct mem_section **mem_section;
>>> +extern struct mem_section **mem_sections;
>>> #else
>>> -extern struct mem_section mem_section[NR_SECTION_ROOTS][SECTIONS_PER_ROOT];
>>> +extern struct mem_section mem_sections[NR_SECTION_ROOTS][SECTIONS_PER_ROOT];
>>> #endif
>>>
>>> static inline unsigned long *section_to_usemap(struct mem_section *ms)
>>> @@ -1315,12 +1315,12 @@ static inline unsigned long *section_to_usemap(struct mem_section *ms)
>>> static inline struct mem_section *__nr_to_section(unsigned long nr)
>>> {
>>> #ifdef CONFIG_SPARSEMEM_EXTREME
>>> - if (!mem_section)
>>> + if (!mem_sections)
>>> return NULL;
>>> #endif
>>> - if (!mem_section[SECTION_NR_TO_ROOT(nr)])
>>> + if (!mem_sections[SECTION_NR_TO_ROOT(nr)])
>>> return NULL;
>>> - return &mem_section[SECTION_NR_TO_ROOT(nr)][nr & SECTION_ROOT_MASK];
>>> + return &mem_sections[SECTION_NR_TO_ROOT(nr)][nr & SECTION_ROOT_MASK];
>>> }
>>> extern unsigned long __section_nr(struct mem_section *ms);
>>> extern size_t mem_section_usage_size(void);
>>> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
>>> index 29cc15398ee4..fb1180d81b5a 100644
>>> --- a/kernel/crash_core.c
>>> +++ b/kernel/crash_core.c
>>> @@ -414,8 +414,8 @@ static int __init crash_save_vmcoreinfo_init(void)
>>> VMCOREINFO_SYMBOL(contig_page_data);
>>> #endif
>>> #ifdef CONFIG_SPARSEMEM
>>> - VMCOREINFO_SYMBOL_ARRAY(mem_section);
>>> - VMCOREINFO_LENGTH(mem_section, NR_SECTION_ROOTS);
>>> + VMCOREINFO_SYMBOL_ARRAY(mem_sections);
>>> + VMCOREINFO_LENGTH(mem_sections, NR_SECTION_ROOTS);
>>> VMCOREINFO_STRUCT_SIZE(mem_section);
>>> VMCOREINFO_OFFSET(mem_section, section_mem_map);
>>> VMCOREINFO_NUMBER(MAX_PHYSMEM_BITS);
>>> diff --git a/mm/sparse.c b/mm/sparse.c
>>> index d02ee6bb7cbc..6412010478f7 100644
>>> --- a/mm/sparse.c
>>> +++ b/mm/sparse.c
>>> @@ -24,12 +24,12 @@
>>> * 1) mem_section - memory sections, mem_map's for valid memory
>>> */
>>> #ifdef CONFIG_SPARSEMEM_EXTREME
>>> -struct mem_section **mem_section;
>>> +struct mem_section **mem_sections;
>>> #else
>>> -struct mem_section mem_section[NR_SECTION_ROOTS][SECTIONS_PER_ROOT]
>>> +struct mem_section mem_sections[NR_SECTION_ROOTS][SECTIONS_PER_ROOT]
>>> ____cacheline_internodealigned_in_smp;
>>> #endif
>>> -EXPORT_SYMBOL(mem_section);
>>> +EXPORT_SYMBOL(mem_sections);
>>>
>>> #ifdef NODE_NOT_IN_PAGE_FLAGS
>>> /*
>>> @@ -66,8 +66,8 @@ static void __init sparse_alloc_section_roots(void)
>>>
>>> size = sizeof(struct mem_section *) * NR_SECTION_ROOTS;
>>> align = 1 << (INTERNODE_CACHE_SHIFT);
>>> - mem_section = memblock_alloc(size, align);
>>> - if (!mem_section)
>>> + mem_sections = memblock_alloc(size, align);
>>> + if (!mem_sections)
>>> panic("%s: Failed to allocate %lu bytes align=0x%lx\n",
>>> __func__, size, align);
>>> }
>>> @@ -103,14 +103,14 @@ static int __meminit sparse_index_init(unsigned long section_nr, int nid)
>>> *
>>> * The mem_hotplug_lock resolves the apparent race below.
>>> */
>>> - if (mem_section[root])
>>> + if (mem_sections[root])
>>> return 0;
>>>
>>> section = sparse_index_alloc(nid);
>>> if (!section)
>>> return -ENOMEM;
>>>
>>> - mem_section[root] = section;
>>> + mem_sections[root] = section;
>>>
>>> return 0;
>>> }
>>> @@ -145,7 +145,7 @@ unsigned long __section_nr(struct mem_section *ms)
>>> #else
>>> unsigned long __section_nr(struct mem_section *ms)
>>> {
>>> - return (unsigned long)(ms - mem_section[0]);
>>> + return (unsigned long)(ms - mem_sections[0]);
>>> }
>>> #endif
>>>
>>>
>>
>> I repeat: unnecessary code churn IMHO.
>
> Hi David,
>
> Thanks, i explained the reason during my last reply.
> Andrew has already picked this patch to -mm tree.
Just because it's in Andrews tree doesn't mean it will end up upstream. ;)
Anyhow, no really strong opinion, it's simply unnecessary code churn
that makes bisecting harder without real value IMHO.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-06-01 8:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 9:19 [PATCH V2 0/6] mm/sparse: a few minor fixes and improvements Dong Aisheng
2021-05-31 9:19 ` [PATCH V2 1/6] mm: drop SECTION_SHIFT in code comments Dong Aisheng
2021-05-31 9:19 ` [PATCH V2 2/6] mm/sparse: free section usage memory in case populate_section_memmap failed Dong Aisheng
2021-05-31 15:06 ` Liam Howlett
2021-06-01 2:37 ` Dong Aisheng
2021-06-01 8:19 ` David Hildenbrand
2021-05-31 9:19 ` [PATCH V2 3/6] mm/sparse: move mem_sections allocation out of memory_present() Dong Aisheng
2021-05-31 14:39 ` Liam Howlett
2021-06-01 2:38 ` Dong Aisheng
2021-06-01 8:22 ` David Hildenbrand
2021-05-31 9:19 ` [PATCH V2 4/6] mm: rename the global section array to mem_sections Dong Aisheng
2021-06-01 8:22 ` David Hildenbrand
2021-06-01 8:37 ` Dong Aisheng
2021-06-01 8:40 ` David Hildenbrand [this message]
2021-06-01 8:44 ` Dong Aisheng
2021-06-01 23:52 ` Andrew Morton
2021-06-02 1:11 ` HAGIO KAZUHITO(萩尾 一仁)
2021-06-02 2:26 ` Andrew Morton
2021-06-02 3:03 ` Baoquan He
2021-06-02 5:02 ` HAGIO KAZUHITO(萩尾 一仁)
2021-06-02 5:22 ` Baoquan He
2021-05-31 9:19 ` [PATCH V2 5/6] mm/page_alloc: improve memmap_pages dbg msg Dong Aisheng
2021-06-01 8:23 ` David Hildenbrand
2021-05-31 9:19 ` [PATCH V2 6/6] mm/sparse: remove one duplicated #ifdef CONFIG_SPARSEMEM_EXTREME Dong Aisheng
2021-06-01 8:26 ` David Hildenbrand
2021-06-01 8:39 ` Dong Aisheng
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=f7f77368-72cf-e15d-cc3c-b0ddf86e14fd@redhat.com \
--to=david@redhat.com \
--cc=aisheng.dong@nxp.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dongas86@gmail.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vgoyal@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).