From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Alistair Popple <apopple@nvidia.com>, akpm@linux-foundation.org
Cc: jhubbard@nvidia.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, ziy@nvidia.com
Subject: Re: [PATCH] mm/pages_alloc.c: Don't create ZONE_MOVABLE beyond the end of a node
Date: Tue, 15 Feb 2022 10:17:09 +0530 [thread overview]
Message-ID: <7b752e06-f345-cbb2-d05c-57e5fc5d8e5a@arm.com> (raw)
In-Reply-To: <20220215025831.2113067-1-apopple@nvidia.com>
Hi Alistair,
On 2/15/22 8:28 AM, Alistair Popple wrote:
> ZONE_MOVABLE uses the remaining memory in each node. It's starting pfn
> is also aligned to MAX_ORDER_NR_PAGES. It is possible for the remaining
> memory in a node to be less than MAX_ORDER_NR_PAGES, meaning there is
> not enough room for ZONE_MOVABLE on that node.
How plausible is this scenario on normal systems ? Should not the node
always contain MAX_ORDER_NR_PAGES aligned pages ? Also all zones which
get created from that node should also be MAX_ORDER_NR_PAGES aligned ?
I am just curious how a node could end up being like this.
- Anshuman
next prev parent reply other threads:[~2022-02-15 4:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 2:58 [PATCH] mm/pages_alloc.c: Don't create ZONE_MOVABLE beyond the end of a node Alistair Popple
2022-02-15 4:47 ` Anshuman Khandual [this message]
2022-02-15 5:16 ` Alistair Popple
2022-02-16 5:24 ` Anshuman Khandual
2022-02-15 6:15 ` Oscar Salvador
2022-02-17 7:48 ` David Hildenbrand
2022-02-21 11:20 ` 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=7b752e06-f345-cbb2-d05c-57e5fc5d8e5a@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ziy@nvidia.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).