From: Andrew Morton <akpm@linux-foundation.org>
To: Oscar Salvador <osalvador@techadventures.net>
Cc: mhocko@suse.com, vbabka@suse.cz, Pavel.Tatashin@microsoft.com,
sfr@canb.auug.org.au, iamjoonsoo.kim@lge.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Oscar Salvador <osalvador@suse.de>,
Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH] mm/page_alloc: Clean up check_for_memory
Date: Tue, 28 Aug 2018 14:35:30 -0700 [thread overview]
Message-ID: <20180828143530.4b681bf9e0b3c03519fbe943@linux-foundation.org> (raw)
In-Reply-To: <20180828210158.4617-1-osalvador@techadventures.net>
On Tue, 28 Aug 2018 23:01:58 +0200 Oscar Salvador <osalvador@techadventures.net> wrote:
> From: Oscar Salvador <osalvador@suse.de>
>
> check_for_memory looks a bit confusing.
> First of all, we have this:
>
> if (N_MEMORY == N_NORMAL_MEMORY)
> return;
>
> Checking the ENUM declaration, looks like N_MEMORY canot be equal to
> N_NORMAL_MEMORY.
> I could not find where N_MEMORY is set to N_NORMAL_MEMORY, or the other
> way around either, so unless I am missing something, this condition
> will never evaluate to true.
> It makes sense to get rid of it.
Added by
commit 4b0ef1fe8a626f0ba7f649764f979d0dc9eab86b
Author: Lai Jiangshan <laijs@cn.fujitsu.com>
AuthorDate: Wed Dec 12 13:51:46 2012 -0800
Commit: Linus Torvalds <torvalds@linux-foundation.org>
CommitDate: Wed Dec 12 17:38:33 2012 -0800
page_alloc: use N_MEMORY instead N_HIGH_MEMORY change the node_states initia
lization
Let's cc Lai Jiangshan, see if he can remmeber the reasoning.
But yes, it does look like im-not-sure-whats-going-on-here
defensiveness.
> Moving forward, the operations whithin the loop look a bit confusing
> as well.
>
> We set N_HIGH_MEMORY unconditionally, and then we set N_NORMAL_MEMORY
> in case we have CONFIG_HIGHMEM (N_NORMAL_MEMORY != N_HIGH_MEMORY)
> and zone <= ZONE_NORMAL.
> (N_HIGH_MEMORY falls back to N_NORMAL_MEMORY on !CONFIG_HIGHMEM systems,
> and that is why we can just go ahead and set N_HIGH_MEMORY unconditionally)
>
> Although this works, it is a bit subtle.
>
> I think that this could be easier to follow:
>
> First, we should only set N_HIGH_MEMORY in case we have
> CONFIG_HIGHMEM.
Why? Just a teeny optimization?
> And then we should set N_NORMAL_MEMORY in case zone <= ZONE_NORMAL,
> without further checking whether we have CONFIG_HIGHMEM or not.
>
> Signed-off-by: Oscar Salvador <osalvador@suse.de>
> ---
> mm/page_alloc.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 839e0cc17f2c..6aa947f9e614 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -6819,15 +6819,12 @@ static void check_for_memory(pg_data_t *pgdat, int nid)
> {
> enum zone_type zone_type;
>
> - if (N_MEMORY == N_NORMAL_MEMORY)
> - return;
> -
> for (zone_type = 0; zone_type <= ZONE_MOVABLE - 1; zone_type++) {
> struct zone *zone = &pgdat->node_zones[zone_type];
> if (populated_zone(zone)) {
> - node_set_state(nid, N_HIGH_MEMORY);
> - if (N_NORMAL_MEMORY != N_HIGH_MEMORY &&
> - zone_type <= ZONE_NORMAL)
> + if (IS_ENABLED(CONFIG_HIGHMEM))
> + node_set_state(nid, N_HIGH_MEMORY);
> + if (zone_type <= ZONE_NORMAL)
> node_set_state(nid, N_NORMAL_MEMORY);
> break;
> }
next prev parent reply other threads:[~2018-08-28 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 21:01 Oscar Salvador
2018-08-28 21:35 ` Andrew Morton [this message]
2018-08-29 20:34 ` Oscar Salvador
2018-08-30 1:55 ` Pasha Tatashin
2018-08-31 12:24 ` Oscar Salvador
2018-08-31 14:04 ` Pasha Tatashin
2018-08-31 20:45 ` Oscar Salvador
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=20180828143530.4b681bf9e0b3c03519fbe943@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Pavel.Tatashin@microsoft.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=osalvador@techadventures.net \
--cc=sfr@canb.auug.org.au \
--cc=vbabka@suse.cz \
/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