From: Mel Gorman <mgorman@techsingularity.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
Michal Hocko <mhocko@kernel.org>,
Jesper Dangaard Brouer <brouer@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Mel Gorman <mgorman@techsingularity.net>
Subject: [PATCH 0/2] Allow high order pages to be stored on PCP v2
Date: Thu, 3 Jun 2021 15:22:18 +0100 [thread overview]
Message-ID: <20210603142220.10851-1-mgorman@techsingularity.net> (raw)
Changelog since v1
o Better comments and macros (vbabka)
o Fix pindex_to_order (vbabka)
The per-cpu page allocator (PCP) only handles order-0 pages. With the
series "Use local_lock for pcp protection and reduce stat overhead"
and "Calculate pcp->high based on zone sizes and active CPUs", it's now
feasible to store high-order pages on PCP lists.
This small series allows PCP to store "cheap" orders where cheap is
determined by PAGE_ALLOC_COSTLY_ORDER and THP-sized allocations. For
convenience, the series with the prerequisites are at
git://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git mm-pcphighorder-v2r1
The baseline is 5.13-rc2 because that is what I tested with but the
patches rebase cleanly to mmots.
include/linux/mmzone.h | 20 ++++-
mm/internal.h | 2 +-
mm/page_alloc.c | 171 +++++++++++++++++++++++++++++------------
mm/swap.c | 2 +-
4 files changed, 141 insertions(+), 54 deletions(-)
--
2.26.2
next reply other threads:[~2021-06-03 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 14:22 Mel Gorman [this message]
2021-06-03 14:22 ` [PATCH 1/2] mm/page_alloc: Move free_the_page Mel Gorman
2021-06-03 14:22 ` [PATCH 2/2] mm/page_alloc: Allow high-order pages to be stored on the per-cpu lists Mel Gorman
2021-06-09 18:30 ` Zi Yan
2021-06-10 11:18 ` Mel Gorman
2021-06-10 11:40 ` Zi Yan
2021-06-10 22:59 ` Andrew Morton
2021-06-11 0:38 ` Stephen Rothwell
2021-06-11 8:10 ` Mel Gorman
2021-06-11 8:34 ` Mel Gorman
2021-06-11 12:17 ` Zi Yan
2021-06-11 13:58 ` Mel Gorman
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=20210603142220.10851-1-mgorman@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).