From: Andrew Morton <akpm@linux-foundation.org>
To: Kiryl Shutsemau <kirill@shutemov.name>
Cc: Vlastimil Babka <vbabka@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
David Hildenbrand <david@kernel.org>,
Harry Yoo <harry@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <brendan.jackman@linux.dev>,
Zi Yan <ziy@nvidia.com>, Shakeel Butt <shakeel.butt@linux.dev>,
Usama Arif <usama.arif@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2] mm: page_alloc: make defrag_mode retries follow the promoted order
Date: Wed, 7 Oct 2026 11:32:12 -0700 [thread overview]
Message-ID: <20261007113212.1fa804db80cc6f534ca01a59@linux-foundation.org> (raw)
In-Reply-To: <asZCEttmL6VlMXKc@thinkstation>
On Wed, 7 Oct 2026 14:01:33 +0100 Kiryl Shutsemau <kirill@shutemov.name> wrote:
> > > v2:
> > > - keep the compaction priority floor and the COMPACT_SUCCESS retry
> > > limit on the request order, so non-costly requests still escalate to
> > > SYNC_FULL before falling back (Harry Yoo, Johannes Weiner)
> > > - compute the promoted order once in __alloc_pages_slowpath() and pass
> > > it to direct reclaim, direct compaction and the retry helpers, instead
> > > of each of them deriving it (Harry Yoo)
> >
> > Thanks. That's a fairly large update. v2 diff is below.
> >
> > Are we sure about cc:stable? Or even 7.3-rcX? It's a pretty big
> > change.
>
> I think defrag_mode is not widely used. Maybe only in Meta.
>
> What about keeping cc:stable, but only submit it to Linus for v7.4-rc1?
>
> By the time we would have the patch battle-tested in the fleet.
OK, let's do that.
next prev parent reply other threads:[~2026-10-07 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 9:18 Kiryl Shutsemau
2026-10-06 23:41 ` Andrew Morton
2026-10-07 13:01 ` Kiryl Shutsemau
2026-10-07 18:32 ` Andrew Morton [this message]
2026-10-07 15:53 ` Usama Arif
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=20261007113212.1fa804db80cc6f534ca01a59@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=brendan.jackman@linux.dev \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=harry@kernel.org \
--cc=kernel-team@meta.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.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
all inboxes | Powered by JetHome®