From: Baoquan He <bhe@redhat.com>
To: js1304@gmail.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Minchan Kim <minchan@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
kernel-team@lge.com, Ye Xiaolong <xiaolong.ye@intel.com>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH v4 2/2] mm/page_alloc: integrate classzone_idx and high_zoneidx
Date: Mon, 23 Mar 2020 15:09:52 +0800 [thread overview]
Message-ID: <20200323070952.GF3039@MiWiFi-R3L-srv> (raw)
In-Reply-To: <1584938972-7430-3-git-send-email-iamjoonsoo.kim@lge.com>
On 03/23/20 at 01:49pm, js1304@gmail.com wrote:
> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
> classzone_idx is just different name for high_zoneidx now.
> So, integrate them and add some comment to struct alloc_context
> in order to reduce future confusion about the meaning of this variable.
>
> The accessor, ac_classzone_idx() is also removed since it isn't needed
> after integration.
>
> In addition to integration, this patch also renames high_zoneidx
> to highest_zoneidx since it represents more precise meaning.
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
The patch looks good, and did the basic test after applying this patch
series. FWIW:
Reviewed-by: Baoquan He <bhe@redhat.com>
next prev parent reply other threads:[~2020-03-23 7:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 4:49 [PATCH v4 0/2] integrate classzone_idx and high_zoneidx js1304
2020-03-23 4:49 ` [PATCH v4 1/2] mm/page_alloc: use ac->high_zoneidx for classzone_idx js1304
2020-03-23 7:08 ` Baoquan He
2020-03-23 4:49 ` [PATCH v4 2/2] mm/page_alloc: integrate classzone_idx and high_zoneidx js1304
2020-03-23 5:21 ` Baoquan He
2020-03-23 5:40 ` Baoquan He
2020-03-23 5:58 ` Joonsoo Kim
2020-03-23 7:09 ` Baoquan He [this message]
2020-03-25 15:20 ` Vlastimil Babka
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=20200323070952.GF3039@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=xiaolong.ye@intel.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).