From: Andrew Morton <akpm@linux-foundation.org>
To: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Tejun Heo <tj@kernel.org>, Tang Chen <tangchen@cn.fujitsu.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [RFC] mm: memblock: change default cnt for regions from 1 to 0
Date: Thu, 23 Oct 2014 12:18:40 -0700 [thread overview]
Message-ID: <20141023121840.f88439912f23a3c2a01eb54f@linux-foundation.org> (raw)
In-Reply-To: <1414083413-61756-1-git-send-email-Zubair.Kakakhel@imgtec.com>
(cc's added)
On Thu, 23 Oct 2014 17:56:53 +0100 Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> wrote:
> The default region counts are set to 1 with a comment saying empty
> dummy entry.
>
> If this is a dummy entry, should this be changed to 0?
>
> We have faced this in mips/kernel/setup.c arch_mem_init.
>
> cma uses memblock. But even with cma disabled.
> The for_each_memblock(reserved, reg) goes inside the loop.
> Even without any reserved regions.
>
> Traced it to the following, when the macro
> for_each_memblock(memblock_type, region) is used.
>
> It expands to add the cnt variable.
>
> for (region = memblock.memblock_type.regions; \
> region < (memblock.memblock_type.regions + memblock.memblock_type.cnt); \
> region++)
>
> In the corner case, that there are no reserved regions.
> Due to the default 1 value of cnt.
> The loop under for_each_memblock still runs once.
>
> Even when there is no reserved region.
>
> Is this by design? or unintentional?
> It might be that this loop runs an extra time every instance out there?
> ---
> mm/memblock.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 6d2f219..b91301c 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -33,16 +33,16 @@ static struct memblock_region memblock_physmem_init_regions[INIT_PHYSMEM_REGIONS
>
> struct memblock memblock __initdata_memblock = {
> .memory.regions = memblock_memory_init_regions,
> - .memory.cnt = 1, /* empty dummy entry */
> + .memory.cnt = 0, /* empty dummy entry */
> .memory.max = INIT_MEMBLOCK_REGIONS,
>
> .reserved.regions = memblock_reserved_init_regions,
> - .reserved.cnt = 1, /* empty dummy entry */
> + .reserved.cnt = 0, /* empty dummy entry */
> .reserved.max = INIT_MEMBLOCK_REGIONS,
>
> #ifdef CONFIG_HAVE_MEMBLOCK_PHYS_MAP
> .physmem.regions = memblock_physmem_init_regions,
> - .physmem.cnt = 1, /* empty dummy entry */
> + .physmem.cnt = 0, /* empty dummy entry */
> .physmem.max = INIT_PHYSMEM_REGIONS,
> #endif
>
> --
> 1.9.1
--
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 prev parent reply other threads:[~2014-10-23 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 16:56 Zubair Lutfullah Kakakhel
2014-10-23 19:18 ` Andrew Morton [this message]
2014-10-27 14:17 ` Tejun Heo
2014-10-27 14:38 ` Zubair Lutfullah Kakakhel
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=20141023121840.f88439912f23a3c2a01eb54f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tangchen@cn.fujitsu.com \
--cc=tj@kernel.org \
--cc=yinghai@kernel.org \
/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