linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: David Hildenbrand <david@redhat.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mel Gorman <mgorman@suse.de>, Vlastimil Babka <vbabka@suse.cz>,
	linux-mm@kvack.org, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page_alloc: Make deferred page init free pages in MAX_ORDER blocks
Date: Fri, 17 Mar 2023 23:08:49 +0300	[thread overview]
Message-ID: <20230317200849.gjqezmeaiqkfz7so@box.shutemov.name> (raw)
In-Reply-To: <373b22c7-9162-eff0-1f0c-0a8d79a8b372@redhat.com>

On Fri, Mar 17, 2023 at 06:50:17PM +0100, David Hildenbrand wrote:
> On 17.03.23 16:35, Kirill A. Shutemov wrote:
> > Normal page init path frees pages during the boot in MAX_ORDER chunks,
> > but deferred page init path does it in pageblock blocks.
> > 
> > Change deferred page init path to work in MAX_ORDER blocks.
> > 
> > For cases when pageblock is larger than MAX_ORDER, set migrate type to
> > MIGRATE_MOVABLE for all pageblocks covered by the page.
> 
> See
> 
> commit b3d40a2b6d10c9d0424d2b398bf962fb6adad87e
> Author: David Hildenbrand <david@redhat.com>
> Date:   Tue Mar 22 14:43:20 2022 -0700
> 
>     mm: enforce pageblock_order < MAX_ORDER
>     Some places in the kernel don't really expect pageblock_order >=
>     MAX_ORDER, and it looks like this is only possible in corner cases:
>     1) CONFIG_DEFERRED_STRUCT_PAGE_INIT we'll end up freeing pageblock_order
>        pages via __free_pages_core(), which cannot possibly work.
> 
>     ...
> 
> How should it still happen?

I got the sentence backwards. It suppose to be

	For cases when MAX_ORDER is larger than pageblock, set migrate type to
	MIGRATE_MOVABLE for all pageblocks covered by the page.


-- 
  Kiryl Shutsemau / Kirill A. Shutemov


  reply	other threads:[~2023-03-17 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 15:35 Kirill A. Shutemov
2023-03-17 17:50 ` David Hildenbrand
2023-03-17 20:08   ` Kirill A. Shutemov [this message]
2023-03-21 16:44 ` 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=20230317200849.gjqezmeaiqkfz7so@box.shutemov.name \
    --to=kirill@shutemov.name \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --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