From: js1304@gmail.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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: [PATCH v3 0/2] integrate classzone_idx and high_zoneidx
Date: Fri, 20 Mar 2020 17:32:13 +0900 [thread overview]
Message-ID: <1584693135-4396-1-git-send-email-iamjoonsoo.kim@lge.com> (raw)
From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Hello,
This patchset is follow-up of the problem reported and discussed
two years ago [1, 2]. The problem this patchset solves is related to
the classzone_idx on the NUMA system. It causes a problem when
the lowmem reserve protection exists for some zones on a node
that do not exist on other nodes.
This problem is reported two years ago, and, at that time,
the solution got general agreements [2]. But, due to my laziness,
it's not upstreamed. Now, I tried again. This patchset is based on
next-20200317 git tree.
Thanks.
Changes on v3
- improve the commit message
- remove useless accessor, ac_classzone_idx()
[1]: http://lkml.kernel.org/r/20180102063528.GG30397@yexl-desktop
[2]: http://lkml.kernel.org/r/1525408246-14768-1-git-send-email-iamjoonsoo.kim@lge.com
Joonsoo Kim (2):
mm/page_alloc: use ac->high_zoneidx for classzone_idx
mm/page_alloc: integrate classzone_idx and high_zoneidx
include/linux/compaction.h | 9 ++--
include/linux/mmzone.h | 12 ++---
include/trace/events/compaction.h | 22 ++++----
include/trace/events/vmscan.h | 14 +++--
mm/compaction.c | 64 +++++++++++------------
mm/internal.h | 21 +++++---
mm/memory_hotplug.c | 6 +--
mm/oom_kill.c | 4 +-
mm/page_alloc.c | 60 +++++++++++-----------
mm/slab.c | 4 +-
mm/slub.c | 4 +-
mm/vmscan.c | 105 ++++++++++++++++++++------------------
12 files changed, 175 insertions(+), 150 deletions(-)
--
2.7.4
next reply other threads:[~2020-03-20 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 8:32 js1304 [this message]
2020-03-20 8:32 ` [PATCH v3 1/2] mm/page_alloc: use ac->high_zoneidx for classzone_idx js1304
2020-03-20 10:30 ` Baoquan He
2020-03-23 3:50 ` Joonsoo Kim
2020-03-23 3:58 ` Baoquan He
2020-03-23 4:18 ` Joonsoo Kim
2020-03-20 8:32 ` [PATCH v3 2/2] mm/page_alloc: integrate classzone_idx and high_zoneidx js1304
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=1584693135-4396-1-git-send-email-iamjoonsoo.kim@lge.com \
--to=js1304@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.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).