linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Vlastimil Babka <vbabka@suse.cz>,
	linux-kernel@vger.kernel.org,
	Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	Zi Yan <ziy@nvidia.com>, Yu Zhao <yuzhao@google.com>
Subject: Re: [PATCH v1 1/2] mm/page_alloc: conditionally split > pageblock_order pages in free_one_page() and move_freepages_block_isolate()
Date: Tue, 10 Dec 2024 10:39:44 +0100	[thread overview]
Message-ID: <20245acc-1d2e-4166-ab78-6b1614d4e47c@redhat.com> (raw)
In-Reply-To: <e1a898ba-a717-4d20-9144-29df1a6c8813@suse.cz>

On 09.12.24 20:01, Vlastimil Babka wrote:
> On 12/6/24 10:59, David Hildenbrand wrote:
>> Let's special-case for the common scenarios that:
>>
>> (a) We are freeing pages <= pageblock_order
>> (b) We are freeing a page <= MAX_PAGE_ORDER and all pageblocks match
>>      (especially, no mixture of isolated and non-isolated pageblocks)
> 
> Well in many of those cases we could also just adjust the pageblocks... But
> perhaps they indeed shouldn't differ in the first place, unless there's an
> isolation attempt.

Thanks for the review and finding that one flaw.

Yes, I agree: usually we expect this to only happen with isolated 
pageblocks. At least in the scenarios I have in mind (boot, hotplug, 
alloc_contig_range()), we should only ever have a mixture of isolated 
and !isolated.

Maybe one could even special case on zone->nr_isolate_pageblock: if 0, 
just assume all pageblocks are the equal. I'll look into some details 
and might send a follow-up patch.

-- 
Cheers,

David / dhildenb



  parent reply	other threads:[~2024-12-10  9:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06  9:59 [PATCH v1 0/2] mm/page_alloc: rework conditional splitting >= pageblock_order pages when freeing David Hildenbrand
2024-12-06  9:59 ` [PATCH v1 1/2] mm/page_alloc: conditionally split > pageblock_order pages in free_one_page() and move_freepages_block_isolate() David Hildenbrand
2024-12-06 16:58   ` Zi Yan
2024-12-07  6:48   ` Yu Zhao
2024-12-09 19:01   ` Vlastimil Babka
2024-12-09 19:23     ` Zi Yan
2024-12-09 21:35       ` David Hildenbrand
2024-12-09 21:42         ` Zi Yan
2024-12-09 22:10           ` David Hildenbrand
2024-12-09 21:36       ` Vlastimil Babka
2024-12-10  9:39     ` David Hildenbrand [this message]
2024-12-06  9:59 ` [PATCH v1 2/2] mm/page_isolation: fixup isolate_single_pageblock() comment regarding splitting free pages David Hildenbrand
2024-12-06 16:59   ` Zi Yan
2024-12-09 22:13   ` 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=20245acc-1d2e-4166-ab78-6b1614d4e47c@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    --cc=yuzhao@google.com \
    --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